Re: Back-dating commits--way back--for constitution.git

From: Joel C. Salomon <joelcsalomon@gmail.com>
Date: Aug 6, 2010, 15:29 UTC
Message-ID: <AANLkTik2fem_=vN1J52z+QqtCamxNhHAVeG1jxrbSCba@mail.gmail.com>
In-Reply-To: <AANLkTinXtjn7=9jRNmv4zhhPiy3NVOca0gY9dkYCUhY7@mail.gmail.com>

On Fri, Aug 6, 2010 at 11:19 AM, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:

Show 10 quoted lines

> On Fri, Aug 6, 2010 at 15:18, Joel C. Salomon <joelcsalomon@gmail.com> 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@gmail.com> wrote:

Show 7 quoted lines

> On Fri, Aug 6, 2010 at 03:18, Jakub Narebski <jnareb@gmail.com> 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