Thread (5 messages) flat view 5 messages, 3 authors, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: git bugs · Junio C Hamano <hidden> · 2016-06-15
  • Re: git bugs · Ben Lynn <hidden> · 2016-06-15
  • Re: git bugs · Ben Lynn <hidden> · 2016-06-15
  • Re: git bugs · Stephen R. van den Berg <hidden> · 2016-06-15
  • Re: git bugs · Ben Lynn <hidden> · 2016-06-15

Re: git bugs

From: Ben Lynn <hidden>
Date: 2016-06-15 22:44:43

Thanks everyone who replied. You know, I was a bit apprehensive about
posting originally, because I had heard the git ML was inflammable.
But all these responses have been prompt, well-thought-out and
informative.

I plan to take all these suggestions and have a go at hacking a
race-free index which updates successfully despite concurrent file
operations.

Thanks again,
-Ben

On Wed, Jun 11, 2008 at 5:46 AM, Stephen R. van den Berg [off-list ref] wrote:
Ben Lynn wrote:
quoted
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.
That basically is as short as it gets, except perhaps statting a freshly
modified file (not necessarily by oneself).
quoted
Are there any guarantees of any kind? e.g. is the filesystem current
time at least never ahead of the system time?
Practically no guarantees, just that it is rather likely for the time at
the fileserver to progress at about the same pace as yours.
--
Sincerely,
          Stephen R. van den Berg.

Differentiation is an integral part of calculus.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help