On Tue, Nov 01, 2011 at 06:13:20AM +0700, Nguyen Thai Ngoc Duy wrote: > On Mon, Oct 31, 2011 at 08:17:09PM +0400, Dmitry V. Levin wrote: > > > > git rev-parse --since=1970-01-01 (and other git commands that take > > date string arguments like --since) may fail when --since=1970-01-01 is > > given. Whether it fails or not depends on current time and timezone data. > > For example, "TZ=Europe/Paris git rev-parse --since=1970-01-01" fails two > > hours a day (between 00:00 and 02:00 CET), and those who use more eastern > > timezones are even less lucky. In artificial timezones like UTC-24 it > > always fails: > > > > $ TZ=UTC-24 git rev-parse --since=1970-01-01 > > --max-age=18446744073709523490 > > Out of curiosity, why do you need to work with a time so close to that > date? There is an utility that used to invoke "git log --since='1970-01-01 UTC'" by default, and I was unlucky enough to use it during these hours of failure. The utility is now fixed (it no longer calls git log with --since option unless explicitly instructed to do so), and I hope git is going to be fixed as well. BTW, the timezone specifier (UTC) in "git rev-parse --since='1970-01-01 UTC'" seems to be completely ignored by date string parser. -- ldv
Attachment:
pgpCvyiVyc1HH.pgp
Description: PGP signature