Mark Levedahl <mlevedahl@xxxxxxxxxxx> writes: > ... Is it the case that > the size info stored in the index reflects the size of the blob rather > than of the working copy? The size field among other fields is to cache the last lstat(2) information so that later "is the path modified?" question can be answered efficiently. So the size should in general match both blob and filesystem but on CRLF filesystems it is compared against and updated with the data from the filesystem. There could be a subtle bug that when updating an index entry we might be incorrectly storing the size of the blob, but I haven't checked. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html