Set line endings on a specific file within my local repository
up vote
0
down vote
favorite
We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
git
asked Nov 22 at 14:15
Behnil
1,51221443
add a comment |
up vote
0
down vote
favorite
We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
git
asked Nov 22 at 14:15
Behnil
1,51221443
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
git
asked Nov 22 at 14:15
Behnil
1,51221443
We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
git
git
asked Nov 22 at 14:15
Behnil
1,51221443
asked Nov 22 at 14:15
Behnil
1,51221443
asked Nov 22 at 14:15
Behnil
1,51221443
asked Nov 22 at 14:15
Behnil
1,51221443
asked Nov 22 at 14:15
Behnil
1,51221443
1,51221443
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.
I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.
Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
I did put attributes file in .git/info folder with content set totask text eol=lfwhere task is name of the file I would like to use withlfline endings, but when I try change line endings in the task file tolfand run git status it still tells me the file task is modified.
– Behnil
Nov 22 at 15:36
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if yougit addthe file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).
– Mark Adelsberger
Nov 22 at 15:44
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.
I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.
Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
I did put attributes file in .git/info folder with content set totask text eol=lfwhere task is name of the file I would like to use withlfline endings, but when I try change line endings in the task file tolfand run git status it still tells me the file task is modified.
– Behnil
Nov 22 at 15:36
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if yougit addthe file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).
– Mark Adelsberger
Nov 22 at 15:44
add a comment |
up vote
0
down vote
accepted
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.
I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.
Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
I did put attributes file in .git/info folder with content set totask text eol=lfwhere task is name of the file I would like to use withlfline endings, but when I try change line endings in the task file tolfand run git status it still tells me the file task is modified.
– Behnil
Nov 22 at 15:36
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if yougit addthe file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).
– Mark Adelsberger
Nov 22 at 15:44
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.
I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.
Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.
I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.
Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.
Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
answered Nov 22 at 14:25
Mark Adelsberger
19.4k11119
19.4k11119
I did put attributes file in .git/info folder with content set totask text eol=lfwhere task is name of the file I would like to use withlfline endings, but when I try change line endings in the task file tolfand run git status it still tells me the file task is modified.
– Behnil
Nov 22 at 15:36
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if yougit addthe file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).
– Mark Adelsberger
Nov 22 at 15:44
add a comment |
I did put attributes file in .git/info folder with content set totask text eol=lfwhere task is name of the file I would like to use withlfline endings, but when I try change line endings in the task file tolfand run git status it still tells me the file task is modified.
– Behnil
Nov 22 at 15:36
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if yougit addthe file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).
– Mark Adelsberger
Nov 22 at 15:44
I did put attributes file in .git/info folder with content set to
task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.– Behnil
Nov 22 at 15:36
I did put attributes file in .git/info folder with content set to
task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.– Behnil
Nov 22 at 15:36
1
1
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you
git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).– Mark Adelsberger
Nov 22 at 15:44
@Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you
git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).– Mark Adelsberger
Nov 22 at 15:44
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53432891%2fset-line-endings-on-a-specific-file-within-my-local-repository%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
