Re: [PATCHv2 1/3] t6022: New test checking for unnecessary updates of renamed+modified files
- From
Elijah Newren <newren@gmail.com>
- Date
- Mar 2, 2011, 22:26 UTC
- Message-ID
- <AANLkTikG+DT3fz3ntqQAz7pzz+aDd2Q4db02C8ypQMx_@mail.gmail.com>
- In-Reply-To
- <4D6CA13C.1000006@viscovery.net>
Hi,
On Tue, Mar 1, 2011 at 12:33 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
> Am 3/1/2011 2:08, schrieb Elijah Newren: > Use > test-chmtime =1000000000 rename &&
<snip>
> orig=$(test-chmtime -v +0 rename) &&
<snip>
Show 6 quoted lines
>> + git diff-files --exit-code # Is "rename" clean, or only racily clean? > > What you see here, is not "racily clean", but "stat dirty". "Racily clean" > means that git thinks that the file is clean (because the stat information > matches), but in fact the file content is not identical to the content > recorded in the index.
Thanks for the suggestions and explanation; I've got it and Jeff's suggestions incorporated.