On Fri, Aug 6, 2010 at 11:19 AM, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote: > On Fri, Aug 6, 2010 at 15:18, Joel C. Salomon <joelcsalomon@xxxxxxxxx> wrote: >> 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. Meanwhile, on Fri, Aug 6, 2010 at 11:08 AM, Sverre Rabbelier <srabbelier@xxxxxxxxx> wrote: > On Fri, Aug 6, 2010 at 03:18, Jakub Narebski <jnareb@xxxxxxxxx> wrote: >> We can *store* it without problems, the problem is with >> *interpretation* by porcelain (and some plumbing). > > That's what I mean though, if the porcelain notices it's trying to > read in a date it can't interpret correctly it should warn the user of > this fact. Seems the error can be checked for when you ask, but I'd rather not have git complain every time I use constitution.git. Aside: I generated the time stamps with <http://github.com/schwern/y2038>, which may be useful for cross-platform y2038 fixes. --Joel -- 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