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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sverre Rabbelier <srabbelier@xxxxxxxxx> writes:
> On Thu, Aug 5, 2010 at 16:58, Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> wrote:
> > 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
> >
> > It would be useful to turn that into a TODO test for Git.
> 
> That's bad, if we can't store a particular date we should do something
> about it, not just silently underflow.

We can *store* it without problems, the problem is with
*interpretation* by porcelain (and some plumbing).

-- 
Jakub Narebski
Poland
ShadeHawk on #git
--
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


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]