Package: git Version: 1:1.7.9.1-1 Severity: wishlist When creating a test repo to demonstrate a problem, I deliberately forced commit dates to the most obvious date -- epoch zero:
$ git filter-branch --env-filter 'export GIT_AUTHOR_DATE="$(TZ=UTC date -d@0 -R)"' $ git rebase -f HEAD~1 Current branch master is up to date, rebase forced. First, rewinding head to replay your work on top of it... Applying: Quux. fatal: invalid date format: 0 +0000 It appears that the zero epoch is special, because using -d@1 works just fine. This is unlikely to bother anyone in the real world, but it seems like a bit of a silly constraint. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git depends on: ii git-man 1:1.7.9.1-1 ii libc6 2.13-27 ii libcurl3-gnutls 7.24.0-1 ii liberror-perl 0.17-1 ii libexpat1 2.0.1-7.2 ii perl-modules 5.14.2-7 ii zlib1g 1:1.2.6.dfsg-2 Versions of packages git recommends: ii less 444-2 ii openssh-client [ssh-client] 1:5.9p1-3 ii patch 2.6.1-3 ii rsync 3.0.9-1 Versions of packages git suggests: pn git-arch <none> pn git-cvs <none> pn git-daemon-run | git-daemon-sysvinit <none> pn git-doc <none> pn git-el <none> pn git-email <none> pn git-gui <none> pn git-svn <none> pn gitk <none> pn gitweb <none> -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org