Re: Git checkout preserve timestamp?

From: Bill Lear <rael@zopyra.com>
Date: Mar 5, 2007, 21:42 UTC
Message-ID: <17900.36569.805689.922989@lisa.zopyra.com>
In-Reply-To: <Pine.LNX.4.63.0703052143120.22628@wbgn013.biozentrum.uni-wuerzburg.de>

On Monday, March 5, 2007 at 21:44:26 (+0100) Johannes Schindelin writes:

Show 14 quoted lines

>Hi,
>
>On Mon, 5 Mar 2007, Bill Lear wrote:
>
>> On Monday, March 5, 2007 at 20:16:35 (+0100) Johannes Schindelin writes:
>>
>> >If somebody (might be even you yourself) pushes into your repo, under 
>> >the name of the branch to which you switch back to right after that. 
>> >Bingo. Files changed.
>> 
>> Yes, they change, and so would the timestamp.  So what?
>
>Think about it. Why would the timestamp change? Because Git wrote the 
>file? But that was exactly the behaviour you were complaining about.

Not because git wrote the file, but because git notices that content changes, and writes the file (and timestamps it) "smartly". If someone writes into the repo, the timestamp stored becomes invalidated and the write of the file just creates the timestamp at the time of the checkout. If no write into the repo index occurs, the stored timestamp is applied after the file is checked out.

Bill