How to remove only file mode from git index
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.
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?
git
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
add a comment |
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.
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?
git
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
add a comment |
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.
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?
git
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
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.
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?
git
git
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
edited Dec 16 at 11:30
Rui F Ribeiro
38.9k1479129
38.9k1479129
asked Jul 18 at 15:30
Александр Комаров
12
asked Jul 18 at 15:30
Александр Комаров
12
asked Jul 18 at 15:30
Александр Комаров
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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...
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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...
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
add a comment |
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...
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
add a comment |
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...
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
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...
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
answered Jul 18 at 15:38
Stephen Kitt
163k24365444
163k24365444
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
