Re: [PATCH] Make use of stat.ctime configurable
- From
David Brown <git@davidb.org>
- Date
- Jul 29, 2008, 01:41 UTC
- Message-ID
- <20080729014120.GA26807@old.davidb.org>
- In-Reply-To
- <7v3alto4r7.fsf@gitster.siamese.dyndns.org>
On Mon, Jul 28, 2008 at 06:31:24PM -0700, Junio C Hamano wrote:
Show 10 quoted lines
>Linus Torvalds <torvalds@linux-foundation.org> writes: > >> The kernel does caching really well, and the kernel is fast as hell, so >> _of_course_ when you benchmark, using kernel data structures looks good, >> especially if you benchmark against code that isn't well written for the >> particular usage case. > >Ok. While I have your attention on st_ctime, let me ask you a stupid >question. Why does "rename(old, new)" change st_ctime when you move a >regular file?
A simple answer might be that posix requires it. But, from the point of view of backup software, not updating the ctime on rename would be horrible, because you'd never know when files got renamed.
David