Ævar Arnfjörð Bjarmason wrote: > On Fri, Aug 6, 2010 at 15:18, Joel C. Salomon <joelcsalomon@xxxxxxxxx> wrote: >> On Thu, Aug 5, 2010 at 5:58 PM, Ævar Arnfjörð Bjarmason >> <avarab@xxxxxxxxx> wrote: >>> On Thu, Aug 5, 2010 at 21:37, Joel C. Salomon <joelcsalomon@xxxxxxxxx> wrote: >>>> It's up, at <http://github.com/jcsalomon/constitution>, with one commit. >>>> >>>> I'm curious to find out if folks with 64-bit time_t get the correct >>>> author and commit times. >>> On 32bit: >>> >>> commit 826a4f7721fe1c3963a733ecbc5422f05925af5d >>> Author: The Philadelphia Convention <> >>> Date: Wed Dec 31 19:59:59 1969 -0400 >>> >>> On 64bit: >>> >>> commit 826a4f7721fe1c3963a733ecbc5422f05925af5d >>> Author: The Philadelphia Convention <> >>> Date: Mon Sep 17 13:00:00 1787 -0400 >> Cool, it works! (The 13:00 should have been 12:00, but there's some >> DST weirdness at work.) >> >> Can you check what git-fsck has to say about the repos, on 32- & >> 64-bit machines? > > 32bit says: > > error in commit 826a4f7721fe1c3963a733ecbc5422f05925af5d: invalid > author/committer line > > 64 bit doesn't give any warning at all. I don't think you're using the latest git. I get this on 64 bit: error in commit 826a4f7721fe1c3963a733ecbc5422f05925af5d: invalid author/committer line - bad date This is triggered by the negative sign '-' in front of the time field which is not one of 0123456789. See fsck.c line 244. -brandon -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html