# Cannot checkout after setting the eol attribute 15 messages from 2017-08-22 to 2017-08-31. Participants: Ben Boeckel, Torsten Bögershausen, Junio C Hamano. Thread: https://gitlist.dev/t/46647 ## Ben Boeckel, 2017-08-22 17:49 Subject: Cannot checkout after setting the eol attribute Message-ID: <20170822174918.GA1005@megas.kitware.com> URL: https://gitlist.dev/e/20170822174918.GA1005%40megas.kitware.com ``` Hi, I specified the `eol` attribute on some files recently and the behavior of Git is very strange. Here is the set of commands to set up the repository used for the discussion: git init echo $'dos\r' > dos git add dos git commit -m "dos newlines" echo "dos -crlf" > .gitattributes git add .gitattributes git commit -m "add attributes" echo "dos eol=crlf" > .gitattributes git add .gitattributes git commit -m "set eol attribute instead" The following behaviors are observed: - `git reset --hard` does not make the working directory clean; and - `git rebase` gets *very* confused about the diffs in the working tree because `git stash` can't reset the working tree; There are probably other oddities lingering about as well. If I commit what Git thinks is the difference, the diff (with invisibles made visible) is: % git diff | cat -A diff --git a/dos b/dos$ index fde2310..4723a1b 100644$ --- a/dos$ +++ b/dos$ @@ -1 +1 @@$ -dos^M$ +dos$ Seen in 2.9.5 and 2.14.0.rc1. --Ben ``` ## Torsten Bögershausen, 2017-08-22 19:13 Subject: Re: Cannot checkout after setting the eol attribute Message-ID: <20170822191318.GA22118@tor.lan> URL: https://gitlist.dev/e/20170822191318.GA22118%40tor.lan In-Reply-To: <20170822174918.GA1005@megas.kitware.com> ``` On Tue, Aug 22, 2017 at 01:49:18PM -0400, Ben Boeckel wrote: > Hi, > > I specified the `eol` attribute on some files recently and the behavior > of Git is very strange. > > Here is the set of commands to set up the repository used for the > discussion: > > git init > echo $'dos\r' > dos > git add dos > git commit -m "dos newlines" > echo "dos -crlf" > .gitattributes > git add .gitattributes > git commit -m "add attributes" > echo "dos eol=crlf" > .gitattributes > git add .gitattributes > git commit -m "set eol attribute instead" > > The following behaviors are observed: > > - `git reset --hard` does not make the working directory clean; and > - `git rebase` gets *very* confused about the diffs in the working > tree because `git stash` can't reset the working tree; > > There are probably other oddities lingering about as well. If I commit > what Git thinks is the difference, the diff (with invisibles made > visible) is: > > % git diff | cat -A > diff --git a/dos b/dos$ > index fde2310..4723a1b 100644$ > --- a/dos$ > +++ b/dos$ > @@ -1 +1 @@$ > -dos^M$ > +dos$ Thanks for the goos example! This is by design. When you set the text attribute (in your case "eol=crlf" implies text) then the file(s) -must- be nomalized and commited so that they have LF in the repo (technically speaking the index) This is what is written about the "eol=crlf" attribute: This setting forces Git to normalize line endings for this file on checkin and convert them to CRLF when the file is checked out. And this is what is implemented in Git. Long story short: The following would solve your problem: git init echo $'dos\r' > dos git add dos git commit -m "dos newlines" echo "dos -crlf" > .gitattributes git add .gitattributes git commit -m "add attributes" echo "dos eol=crlf" > .gitattributes git read-tree --empty # Clean index, force re-scan of working directory git add dos git add .gitattributes git commit -m "set eol attribute instead" git ls-files --eol > > Seen in 2.9.5 and 2.14.0.rc1. > > --Ben ``` ## Ben Boeckel, 2017-08-22 19:44 Subject: Re: Cannot checkout after setting the eol attribute Message-ID: <20170822194441.GA25093@megas.kitware.com> URL: https://gitlist.dev/e/20170822194441.GA25093%40megas.kitware.com In-Reply-To: <20170822191318.GA22118@tor.lan> ``` On Tue, Aug 22, 2017 at 21:13:18 +0200, Torsten Bögershausen wrote: > When you set the text attribute (in your case "eol=crlf" implies text) > then the file(s) -must- be nomalized and commited so that they have LF > in the repo (technically speaking the index) This seems like a special case that Git could detect and message about somehow. > This is what is written about the "eol=crlf" attribute: > This setting forces Git to normalize line endings for this > file on checkin and convert them to CRLF when the file is > checked out. > And this is what is implemented in Git. Yeah, I read the docs, but the oddities of reset not doing its job wasn't clear from this sentence :) . > Long story short: > > The following would solve your problem: > git init > echo $'dos\r' > dos > git add dos > git commit -m "dos newlines" > echo "dos -crlf" > .gitattributes > git add .gitattributes > git commit -m "add attributes" > echo "dos eol=crlf" > .gitattributes > git read-tree --empty # Clean index, force re-scan of working directory The fact that plumbing is necessary to dig yourself out of a hole of the `eol` attribute changes points to something needing to be changed, even if it's only documentation. Could Git detect this and message about it somehow when `git reset` cannot fix the working tree? Or maybe it could at least exit with failure instead of success? --Ben ``` ## Junio C Hamano, 2017-08-22 20:03 Subject: Re: Cannot checkout after setting the eol attribute Message-ID: URL: https://gitlist.dev/e/xmqqziar1iau.fsf%40gitster.mtv.corp.google.com In-Reply-To: <20170822191318.GA22118@tor.lan> ``` Torsten Bögershausen writes: > The following would solve your problem: > git init > echo $'dos\r' > dos > git add dos > git commit -m "dos newlines" > echo "dos -crlf" > .gitattributes > git add .gitattributes > git commit -m "add attributes" > echo "dos eol=crlf" > .gitattributes > git read-tree --empty # Clean index, force re-scan of working directory > git add dos This is not advisable as a general suggestion, as in a real life (as opposed to a toy example) there will be paths other than this 'dos' thing in the working tree. Perhaps replace "git read-tree --empty" with "git rm -f --cached dos" or something like that that limits its damage would prevent mistakes better. > git add .gitattributes > git commit -m "set eol attribute instead" > git ls-files --eol ``` ## Torsten Bögershausen, 2017-08-23 19:43 Subject: Re: Cannot checkout after setting the eol attribute Message-ID: <20170823194315.GA29237@tor.lan> URL: https://gitlist.dev/e/20170823194315.GA29237%40tor.lan In-Reply-To: <20170822194441.GA25093@megas.kitware.com> ``` On Tue, Aug 22, 2017 at 03:44:41PM -0400, Ben Boeckel wrote: > On Tue, Aug 22, 2017 at 21:13:18 +0200, Torsten Bögershausen wrote: > > When you set the text attribute (in your case "eol=crlf" implies text) > > then the file(s) -must- be nomalized and commited so that they have LF > > in the repo (technically speaking the index) > > This seems like a special case that Git could detect and message about > somehow. > > > This is what is written about the "eol=crlf" attribute: > > This setting forces Git to normalize line endings for this > > file on checkin and convert them to CRLF when the file is > > checked out. > > And this is what is implemented in Git. > > Yeah, I read the docs, but the oddities of reset not doing its job > wasn't clear from this sentence :) . git reset does it's job - please see below. The problem is that we need a "git commit" here. After applying .gitattributes, it may be neccessary to "normalize" the files. If there is something in the documentation, that can be improved, please let us know. > > > Long story short: > > > > The following would solve your problem: > > git init > > echo $'dos\r' > dos > > git add dos > > git commit -m "dos newlines" > > echo "dos -crlf" > .gitattributes > > git add .gitattributes > > git commit -m "add attributes" > > echo "dos eol=crlf" > .gitattributes > > git read-tree --empty # Clean index, force re-scan of working directory > > The fact that plumbing is necessary to dig yourself out of a hole of the > `eol` attribute changes points to something needing to be changed, even > if it's only documentation. Could Git detect this and message about it > somehow when `git reset` cannot fix the working tree? The thing is, that the working tree is "in a good state": We want "dos" with CRLF, and that is what we have. There is nothing that can be improved in the working tree. What needs to be fixed, is the index. And that needs to be done with "git add" "git commit." As Junio pointed out, the read-tree is not ideal (to fix a single file in a possible dirty working tree) In your case it looks like this: echo "dos eol=crlf" > .gitattributes git add .gitattributes && git rm --cached dos && git add dos && git commit > Or maybe it could at least exit with failure instead of success? I don't know. It -may- be possible to add a warning in "git reset". I can have a look at that... ``` ## Ben Boeckel, 2017-08-23 21:09 Subject: Re: Cannot checkout after setting the eol attribute Message-ID: <20170823210944.GA32462@megas.kitware.com> URL: https://gitlist.dev/e/20170823210944.GA32462%40megas.kitware.com In-Reply-To: <20170823194315.GA29237@tor.lan> ``` On Wed, Aug 23, 2017 at 21:43:15 +0200, Torsten Bögershausen wrote: > git reset does it's job - please see below. > > The problem is that we need a "git commit" here. > After applying .gitattributes, it may be neccessary to "normalize" the > files. If there is something in the documentation, that can be > improved, please let us know. I'll have a patch up shortly. > On Tue, Aug 22, 2017 at 03:44:41PM -0400, Ben Boeckel wrote: > > The fact that plumbing is necessary to dig yourself out of a hole of the > > `eol` attribute changes points to something needing to be changed, even > > if it's only documentation. Could Git detect this and message about it > > somehow when `git reset` cannot fix the working tree? > > The thing is, that the working tree is "in a good state": > We want "dos" with CRLF, and that is what we have. > There is nothing that can be improved in the working tree. > What needs to be fixed, is the index. And that needs to be done with > "git add" "git commit." > As Junio pointed out, the read-tree is not ideal > (to fix a single file in a possible dirty working tree) > > In your case it looks like this: > > echo "dos eol=crlf" > .gitattributes > git add .gitattributes && > git rm --cached dos && git add dos && > git commit In this case, just adding the file should work: the file is on-disk as intended and adding the file should normalize the line endings when adding it into the index (basically, just `git add dos` should be required to make the index look like it should). > > Or maybe it could at least exit with failure instead of success? > > I don't know. > It -may- be possible to add a warning in "git reset". > I can have a look at that... Thanks. --Ben ``` ## Ben Boeckel, 2017-08-23 21:17 Subject: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170823211741.9633-1-mathstuf@gmail.com> URL: https://gitlist.dev/e/20170823211741.9633-1-mathstuf%40gmail.com In-Reply-To: <20170822174918.GA1005@megas.kitware.com> ``` When setting the `eol` attribute, paths can change their dirty status without any change in the working directory. This can cause confusion and should at least be mentioned with a remedy. Signed-off-by: Ben Boeckel --- Documentation/gitattributes.txt | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt index c4f2be2..3044b71 100644 --- a/Documentation/gitattributes.txt +++ b/Documentation/gitattributes.txt @@ -151,7 +151,11 @@ unspecified. This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line conversion without any -content checks, effectively setting the `text` attribute. +content checks, effectively setting the `text` attribute. Note that +setting this attribute on paths which are in the index with different +line endings than the attribute indicates the paths to be considered +dirty. Adding the path to the index again will normalize the line +endings in the index. Set to string value "crlf":: -- 2.9.5 ``` ## Ben Boeckel, 2017-08-23 21:21 Subject: Re: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170823212142.GA1659@megas.kitware.com> URL: https://gitlist.dev/e/20170823212142.GA1659%40megas.kitware.com In-Reply-To: <20170823211741.9633-1-mathstuf@gmail.com> ``` On Wed, Aug 23, 2017 at 17:17:41 -0400, Ben Boeckel wrote: > diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt > index c4f2be2..3044b71 100644 > --- a/Documentation/gitattributes.txt > +++ b/Documentation/gitattributes.txt > @@ -151,7 +151,11 @@ unspecified. > > This attribute sets a specific line-ending style to be used in the > working directory. It enables end-of-line conversion without any > -content checks, effectively setting the `text` attribute. > +content checks, effectively setting the `text` attribute. Note that > +setting this attribute on paths which are in the index with different > +line endings than the attribute indicates the paths to be considered Oops, missed a "causes" in here. -----------^ I'll wait on uploading a new patch until after feedback on this one. > +dirty. Adding the path to the index again will normalize the line > +endings in the index. --Ben ``` ## Torsten Bögershausen, 2017-08-24 05:50 Subject: Re: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170824055054.GA32617@tor.lan> URL: https://gitlist.dev/e/20170824055054.GA32617%40tor.lan In-Reply-To: <20170823211741.9633-1-mathstuf@gmail.com> ``` On Wed, Aug 23, 2017 at 05:17:41PM -0400, Ben Boeckel wrote: > When setting the `eol` attribute, paths can change their dirty status > without any change in the working directory. This can cause confusion > and should at least be mentioned with a remedy. > > Signed-off-by: Ben Boeckel > --- > Documentation/gitattributes.txt | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt > index c4f2be2..3044b71 100644 > --- a/Documentation/gitattributes.txt > +++ b/Documentation/gitattributes.txt > @@ -151,7 +151,11 @@ unspecified. > > This attribute sets a specific line-ending style to be used in the > working directory. It enables end-of-line conversion without any > -content checks, effectively setting the `text` attribute. > +content checks, effectively setting the `text` attribute. Note that > +setting this attribute on paths which are in the index with different > +line endings than the attribute indicates the paths to be considered > +dirty. Adding the path to the index again will normalize the line > +endings in the index. > There is one minor comment: The problem is when files had been commited with CRLF (regardless what your eol= attribute says) How about something like this : This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line conversion without any -content checks, effectively setting the `text` attribute. +content checks, effectively setting the `text` attribute. Note that +setting this attribute on paths which are in the index with CRLF +line endings makes the paths to be considered dirty. +Adding the path to the index again will normalize the line +endings in the index. ``` ## Ben Boeckel, 2017-08-30 13:49 Subject: Re: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170830134959.GA28282@megas.kitware.com> URL: https://gitlist.dev/e/20170830134959.GA28282%40megas.kitware.com In-Reply-To: <20170824055054.GA32617@tor.lan> ``` On Thu, Aug 24, 2017 at 07:50:54 +0200, Torsten Bögershausen wrote: > This attribute sets a specific line-ending style to be used in the > working directory. It enables end-of-line conversion without any > -content checks, effectively setting the `text` attribute. > +content checks, effectively setting the `text` attribute. Note that > +setting this attribute on paths which are in the index with CRLF > +line endings makes the paths to be considered dirty. > +Adding the path to the index again will normalize the line > +endings in the index. Yes, that sounds better. Will resubmit the patch. --Ben ``` ## Ben Boeckel, 2017-08-30 13:59 Subject: [PATCH v2] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170830135932.1738-1-mathstuf@gmail.com> URL: https://gitlist.dev/e/20170830135932.1738-1-mathstuf%40gmail.com In-Reply-To: <20170822174918.GA1005@megas.kitware.com> ``` When setting the `eol` attribute, paths can change their dirty status without any change in the working directory. This can cause confusion and should at least be mentioned with a remedy. Reviewed-by: Torsten Bögershausen Signed-off-by: Ben Boeckel --- Documentation/gitattributes.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt index c4f2be2..b940d37 100644 --- a/Documentation/gitattributes.txt +++ b/Documentation/gitattributes.txt @@ -151,7 +151,10 @@ unspecified. This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line conversion without any -content checks, effectively setting the `text` attribute. +content checks, effectively setting the `text` attribute. Note that +setting this attribute on paths which are in the index with CRLF line +endings makes the paths to be considered dirty. Adding the path to the +index again will normalize the line endings in the index. Set to string value "crlf":: -- 2.9.5 ``` ## Junio C Hamano, 2017-08-30 21:31 Subject: Re: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: URL: https://gitlist.dev/e/xmqqpobcpwst.fsf%40gitster.mtv.corp.google.com In-Reply-To: <20170824055054.GA32617@tor.lan> ``` Torsten Bögershausen writes: > How about something like this : > > This attribute sets a specific line-ending style to be used in the > working directory. It enables end-of-line conversion without any > -content checks, effectively setting the `text` attribute. > +content checks, effectively setting the `text` attribute. Note that > +setting this attribute on paths which are in the index with CRLF > +line endings makes the paths to be considered dirty. Is this "always makes them dirty" or "may make them dirty depending on the situation"? If the latter, I'd prefer to see s/makes/may make/ here. ``` ## Ben Boeckel, 2017-08-31 13:16 Subject: Re: [PATCH] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170831131644.GB22212@megas.kitware.com> URL: https://gitlist.dev/e/20170831131644.GB22212%40megas.kitware.com In-Reply-To: ``` On Wed, Aug 30, 2017 at 14:31:30 -0700, Junio C Hamano wrote: > Is this "always makes them dirty" or "may make them dirty depending > on the situation"? > > If the latter, I'd prefer to see s/makes/may make/ here. Yes, a coworker reported that some files slipped through this. New patch incoming. --Ben ``` ## Ben Boeckel, 2017-08-31 13:19 Subject: [PATCH v3] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <20170831131936.26226-1-mathstuf@gmail.com> URL: https://gitlist.dev/e/20170831131936.26226-1-mathstuf%40gmail.com In-Reply-To: <20170822174918.GA1005@megas.kitware.com> ``` When setting the `eol` attribute, paths can change their dirty status without any change in the working directory. This can cause confusion and should at least be mentioned with a remedy. Reviewed-by: Torsten Bögershausen Reviewed-by: Junio C Hamano Signed-off-by: Ben Boeckel --- Documentation/gitattributes.txt | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Documentation/gitattributes.txt b/Documentation/gitattributes.txt index c4f2be2..4c68bc1 100644 --- a/Documentation/gitattributes.txt +++ b/Documentation/gitattributes.txt @@ -151,7 +151,10 @@ unspecified. This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line conversion without any -content checks, effectively setting the `text` attribute. +content checks, effectively setting the `text` attribute. Note that +setting this attribute on paths which are in the index with CRLF line +endings may make the paths to be considered dirty. Adding the path to +the index again will normalize the line endings in the index. Set to string value "crlf":: -- 2.9.5 ``` ## Torsten Bögershausen, 2017-08-31 14:33 Subject: Re: [PATCH v3] Documentation: mention that `eol` can change the dirty status of paths Message-ID: <78c1a85a-70c1-ff35-466e-f6c363a0c632@web.de> URL: https://gitlist.dev/e/78c1a85a-70c1-ff35-466e-f6c363a0c632%40web.de In-Reply-To: <20170831131936.26226-1-mathstuf@gmail.com> ``` On 2017-08-31 15:19, Ben Boeckel wrote: > This attribute sets a specific line-ending style to be used in the > working directory. It enables end-of-line conversion without any > -content checks, effectively setting the `text` attribute. > +content checks, effectively setting the `text` attribute. Note that > +setting this attribute on paths which are in the index with CRLF line > +endings may make the paths to be considered dirty. Adding the path to OK - and this leads to another question: Would it make sense if we allow files with "text eol=CRLF" to continue to be stored with CRLF in the index? Skip the normalization for existing files, since the user asked for CRLF in the working tree (and the internal storage is less interesting) Should I consider a patch ? ```