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

Re: bugreport: git does not like subseconds

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 13, 2008, 17:09 UTC
Message-ID
<7v1vxfh7sh.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<alpine.LFD.2.00.0811130842550.3468@nehalem.linux-foundation.org>
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 13 quoted lines
> On Thu, 13 Nov 2008, Jan Engelhardt wrote:
>> 
>> 
>> Git does not like subseconds in $GIT_{AUTHOR,COMMITTER}_DATE,
>> and somehow does time travel instead. Perhaps this is a Glibc
>> limitation? Running openSUSE 11's glibc-2.8(which is actually
>> a 2.7 snapshot I think: glibc-2.8-2008042513.tar.bz2).
>
> This should have been fixed by 9f2b6d2936a7c4bb3155de8efec7b10869ca935e 
> ("date/time: do not get confused by fractional seconds").
>
> But maybe that hasn't made it into any release yet? It's in master, but 
> maybe it never made it into stable? Junio?
No it didn't.

Actually I didn't even think of that as a bug, in the sense that git never accepted fractional seconds and feeding such to git was a user error from day one; iow, 9f2b6d2 (date/time: do not get confused by fractional seconds, 2008-08-16) was an idiotproofing ;-)

But I'd agree perhaps we should cherry pick that one.
Previous: Jan Engelhardt
Message 4 of 4 in “bugreport: git does not like subseconds”
  1. Jan EngelhardtNov 13, 2008
  2. Linus TorvaldsNov 13, 2008
  3. Jan EngelhardtNov 13, 2008
  4. Junio C HamanoNov 13, 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.