Matt McCutchen writes:
> ... may be an important optimization.) If the line endings are changed
> without changing the size or post-conversion content, then no unstaged
> change is reported. It does not appear that git saves the pre-
> conversion content.
Correct. The cached-stat information
On Wed, 2018-02-21 at 08:53 +0100, Torsten Bögershausen wrote:
> I don't hava a pointer, but what should happen ?
> 2 warnings for 2 "git add" should be OK, I think.
>
> 1 warning is part of the optimization, that Git does to handle
> hundrets and thousands of files efficciently.
>
> Is the 1/2 w
On Tue, 2018-02-20 at 08:42 -0500, Matt McCutchen wrote:
> In either case, if "git update-index --refresh" (or "git status") is
> run before "git add", then "git add" does not print the warning. On
> the other hand, if line endings in the working tree file are changed,
> then git shows the file as
On Tue, Feb 20, 2018 at 08:42:26AM -0500, Matt McCutchen wrote:
> I noticed that if a file subject to a safecrlf warning is added to the
> index in the same second that it is created, resulting in a "racily
> clean" index entry, then a subsequent "git add" command prints another
> safecrlf warning.
I noticed that if a file subject to a safecrlf warning is added to the
index in the same second that it is created, resulting in a "racily
clean" index entry, then a subsequent "git add" command prints another
safecrlf warning. I reproduced this on the current "next"
(499d7c4f91). The procedure:
5 matches
Mail list logo
