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

Re: [PATCH] Make reflog query '@{1219188291}' act as '@{2008/08/19 16:24:51}'

From
Alex Riesen <raa.lkml@gmail.com>
Date
Aug 20, 2008, 19:35 UTC
Message-ID
<20080820193557.GB16626@blimp.local>
In-Reply-To
<20080819234433.GJ24212@spearce.org>
Shawn O. Pearce, Wed, Aug 20, 2008 01:44:33 +0200:
Show 5 quoted lines
> The value 1112911993 was chosen for the limit as it is the commit
> timestamp for e83c516331 "Initial revision of "git" ...". Any
> reflogs in existance should contain timestamps dated later than
> the date Linus first stored Git into itself, as reflogs came about
> quite a bit after that.

Maybe I'm missing something, but aren't unsynchronized clocks a common thing in personal computing? Even maybe less common, but noticably frequent, the clocks with the date set way back in the past (by malice or accident)?

Previous: Shawn O. PearceNext: Shawn O. Pearce
Message 4 of 10 in “Make reflog query '@{1219188291}' act as '@{2008/08/19 16:24:51}'”
  1. Make reflog query '@{1219188291}' act as '@{2008/08/19 16:24:51}'Shawn O. Pearce, Aug 19, 2008
  2. Junio C HamanoAug 19, 2008
  3. Shawn O. PearceAug 20, 2008
  4. Alex RiesenAug 20, 2008
  5. Shawn O. PearceAug 20, 2008
  6. Alex RiesenAug 20, 2008
  7. Shawn O. PearceAug 20, 2008
  8. Alex RiesenAug 20, 2008
  9. Junio C HamanoAug 20, 2008
  10. Shawn O. PearceAug 21, 2008

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.