git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: "prune" prone to clock skew (Re: t3306 failure with v1.7.5-rc1)

From
Jeff King <peff@peff.net>
Date
Apr 8, 2011, 18:53 UTC
Message-ID
<20110408185325.GA6337@sigill.intra.peff.net>
In-Reply-To
<7vei5c4lwh.fsf@alter.siamese.dyndns.org>
On Fri, Apr 08, 2011 at 11:51:10AM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> I don't personally think this is worth addressing, but as I was Cc'ed,
> I'll try.
> 
> If we at least know that the object store is contained within a single
> filesystem whose clock is at least guaranteed to monotonically increase,
> one possible workaround would be to touch a garbage file and read its
> timestamp, instead of grabbing the current time from the local clock, no?

Yeah, that is a much more accurate and simpler fix. Like you, I don't really think it's worth worrying about, but if somebody wanted to, that is much better than the fix I mentioned.

-Peff
Previous: Junio C Hamano
Message 7 of 7 in “t3306 failure with v1.7.5-rc1”
  1. Michael J GruberApr 8, 2011
  2. Johannes SixtApr 8, 2011
  3. Michael J GruberApr 8, 2011
  4. "prune" prone to clock skew (Re: t3306 failure with v1.7.5-rc1)Michael J Gruber, Apr 8, 2011
  5. Jeff KingApr 8, 2011
  6. Junio C HamanoApr 8, 2011
  7. Jeff KingApr 8, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.