From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: bugreport: git does not like subseconds
Date: Thu, 13 Nov 2008 08:45:58 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0811130842550.3468@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0811131722360.13330@fbirervta.pbzchgretzou.qr>
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?
Linus
next prev parent reply other threads:[~2008-11-13 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 16:26 bugreport: git does not like subseconds Jan Engelhardt
2008-11-13 16:45 ` Linus Torvalds [this message]
2008-11-13 16:57 ` Jan Engelhardt
2008-11-13 17:09 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.0811130842550.3468@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox