How to remove only file mode from git index

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












Sorry for my English :)
I`m new to work with git. I ititialized git repository and later realized that git indexes file mode such as 777 or 644, and when file mode changes git shows that mode changing and "wants" file to be commited just because its mode was changed.
Please answer me how can I remove the file mode "records" of git index (history) of such file while save it "real" changing history - history of changing its contents?







share|improve this question

























    up vote
    0
    down vote

    favorite












    Sorry for my English :)
    I`m new to work with git. I ititialized git repository and later realized that git indexes file mode such as 777 or 644, and when file mode changes git shows that mode changing and "wants" file to be commited just because its mode was changed.
    Please answer me how can I remove the file mode "records" of git index (history) of such file while save it "real" changing history - history of changing its contents?







    share|improve this question





















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Sorry for my English :)
      I`m new to work with git. I ititialized git repository and later realized that git indexes file mode such as 777 or 644, and when file mode changes git shows that mode changing and "wants" file to be commited just because its mode was changed.
      Please answer me how can I remove the file mode "records" of git index (history) of such file while save it "real" changing history - history of changing its contents?







      share|improve this question











      Sorry for my English :)
      I`m new to work with git. I ititialized git repository and later realized that git indexes file mode such as 777 or 644, and when file mode changes git shows that mode changing and "wants" file to be commited just because its mode was changed.
      Please answer me how can I remove the file mode "records" of git index (history) of such file while save it "real" changing history - history of changing its contents?









      share|improve this question










      share|improve this question




      share|improve this question









      asked Jul 18 at 15:30









      Александр Комаров

      12




      12




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote













          You can achieve this partially by setting core.fileMode to false:



          git config core.fileMode false


          This will cause the executable bit (and only that one) to be ignored.



          Quoting the git-config documentation:




          Tells Git if the executable bit of files in the working tree is to be honored.



          Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary.



          A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1).



          The default is true (when core.filemode is not specified in the config file).




          Whether that’s a good idea is another debate...






          share|improve this answer





















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "106"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457038%2fhow-to-remove-only-file-mode-from-git-index%23new-answer', 'question_page');

            );

            Post as a guest






























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            1
            down vote













            You can achieve this partially by setting core.fileMode to false:



            git config core.fileMode false


            This will cause the executable bit (and only that one) to be ignored.



            Quoting the git-config documentation:




            Tells Git if the executable bit of files in the working tree is to be honored.



            Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary.



            A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1).



            The default is true (when core.filemode is not specified in the config file).




            Whether that’s a good idea is another debate...






            share|improve this answer

























              up vote
              1
              down vote













              You can achieve this partially by setting core.fileMode to false:



              git config core.fileMode false


              This will cause the executable bit (and only that one) to be ignored.



              Quoting the git-config documentation:




              Tells Git if the executable bit of files in the working tree is to be honored.



              Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary.



              A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1).



              The default is true (when core.filemode is not specified in the config file).




              Whether that’s a good idea is another debate...






              share|improve this answer























                up vote
                1
                down vote










                up vote
                1
                down vote









                You can achieve this partially by setting core.fileMode to false:



                git config core.fileMode false


                This will cause the executable bit (and only that one) to be ignored.



                Quoting the git-config documentation:




                Tells Git if the executable bit of files in the working tree is to be honored.



                Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary.



                A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1).



                The default is true (when core.filemode is not specified in the config file).




                Whether that’s a good idea is another debate...






                share|improve this answer













                You can achieve this partially by setting core.fileMode to false:



                git config core.fileMode false


                This will cause the executable bit (and only that one) to be ignored.



                Quoting the git-config documentation:




                Tells Git if the executable bit of files in the working tree is to be honored.



                Some filesystems lose the executable bit when a file that is marked as executable is checked out, or checks out a non-executable file with executable bit on. git-clone(1) or git-init(1) probe the filesystem to see if it handles the executable bit correctly and this variable is automatically set as necessary.



                A repository, however, may be on a filesystem that handles the filemode correctly, and this variable is set to true when created, but later may be made accessible from another environment that loses the filemode (e.g. exporting ext4 via CIFS mount, visiting a Cygwin created repository with Git for Windows or Eclipse). In such a case it may be necessary to set this variable to false. See git-update-index(1).



                The default is true (when core.filemode is not specified in the config file).




                Whether that’s a good idea is another debate...







                share|improve this answer













                share|improve this answer



                share|improve this answer











                answered Jul 18 at 15:38









                Stephen Kitt

                139k22296359




                139k22296359






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f457038%2fhow-to-remove-only-file-mode-from-git-index%23new-answer', 'question_page');

                    );

                    Post as a guest













































































                    Popular posts from this blog

                    How to check contact read email or not when send email to Individual?

                    Bahrain

                    Postfix configuration issue with fips on centos 7; mailgun relay