Re: git bugs
- From
Ben Lynn <benlynn@gmail.com>
- Date
- Jun 11, 2008, 00:24 UTC
- Message-ID
- <832adb090806101724k6199694ftbbc6ed151489a6e3@mail.gmail.com>
- In-Reply-To
- <7vwskwbz63.fsf@gitster.siamese.dyndns.org>
That is problematic. How do I figure out what the filesystem thinks is the current time? I could touch some file and read its mtime, but I want a shortcut.
Are there any guarantees of any kind? e.g. is the filesystem current time at least never ahead of the system time?
-Ben
On Tue, Jun 10, 2008 at 5:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> "Ben Lynn" <benlynn@gmail.com> writes: > >> ... I'm making the same >> assumptions, i.e. files are not touched while they're being indexed. > > Actually you are making another assumption that is somewhat worrysome. > > The filesystem clock and time(2) clock can be skewed and comparing a > timestamp you obtain from lstat(2) and time(2) might not give you any > meaningful information. That is why I made this codepath without using > time(2) when I did the racy-git work. > >