Re: git reset and ctime

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Dec 4, 2010, 01:47 UTC
Message-ID: <20101204014751.GA18629@burratino>
In-Reply-To: <AANLkTi=MSf+0rkBmvuJQBaSs1-G_gFahnLvt44fnwAwf@mail.gmail.com>

ghazel@gmail.com wrote:

> On Fri, Dec 3, 2010 at 4:51 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>> ghazel@gmail.com wrote:

Show 13 quoted lines

>>>              My deploy process (capistrano) maintains a cached copy of
>>> a git repo, which it fetches, resets, and then hardlinks files from
>>> when a deploy occurs ( https://github.com/37signals/fast_remote_cache
>>> ). The hardlinking step is meant to save the time of copying the file.
>>> but hardlinking changes the ctime of the source files.
>>
>> Interesting.  Setting "[core] trustctime = false" in the repository
>> configuration could be a good solution (no performance downside I can
>> think of).
>
> This is a very useful suggestion. I do not see a case where ctime
> would be valuable to me. Is it really valuable to other people? What
> is the trade-off?

Some reading for a rainy day :): [1] and surrounding discussion.

Short answer: I think the main purpose is catching worktree corruption (e.g., if rsync screws up).

[1] http://thread.gmane.org/gmane.comp.version-control.git/89370/focus=89993