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

Re: bugreport: git does not like subseconds

From
JEJan Engelhardt <jengelh@medozas.de>
Date
Nov 13, 2008, 16:57 UTC
Message-ID
<alpine.LNX.1.10.0811131752450.16134@fbirervta.pbzchgretzou.qr>
In-Reply-To
<alpine.LFD.2.00.0811130842550.3468@nehalem.linux-foundation.org>
On Thursday 2008-11-13 17:45, Linus Torvalds wrote:
Show 12 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?
Seems so:

$ git describe 9f2b6d2936a7c4bb3155de8efec7b10869ca935e v1.6.0-3-g9f2b6d2

$ git merge-base 9f2b6d2936a7c4bb3155de8efec7b10869ca935e v1.6.0.3 result: dba9194a49452b5f093b96872e19c91b50e526aa

$ git describe dba9194a49452b5f093b96872e19c91b50e526aa v1.6.0-1-gdba9194

Which means it's not in; -forest also verifies it:

[v1.6.0.x goes here] ^ │ ├ │ │ mailinfo: re-fix MIME multipart boundary parsing │ │ ┌─│─[fix]──date/time: do not get confused by fractional seconds │ │ ├ │ Start 1.6.1 cycle ├─≡───┘ │ ├ │ │ Start 1.6.0.X maintenance series ├─│─────│─[v1.6.0]──GIT 1.6.0

Previous: Linus TorvaldsNext: Junio C Hamano
Message 3 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.