Dnia wtorek 3. sierpnia 2010 09:39, Jakub Narebski napisał:
> Dnia wtorek 3. sierpnia 2010 00:47, Junio C Hamano napisał:
> > Jakub Narebski <jnareb@xxxxxxxxx> writes:
> >
> > > The headers inside commit (and tag) objects are stored in text form,
> > > so they are not limited to 32-bit value. You would have to use system
> > > that has 64-bit time_t, or patch git.
> >
> > I thought the internal representation of our time was "unsigned long", no?
> > How can you represent anything before Unix epoch?
>
> time_t is signed long. Besides, git uses textual representation, its
> just a matter of putting minus sign. We can always fall back to
> low level git-hash-object.
And it works:
$ git show
commit a5f4eaace56c6887846ea77725e1ac6827bb13b0
Author: Jakub Narebski <jnareb@xxxxxxxxx>
Date: Fri May 31 18:24:20 1929 +0200
git-hash-object
$ git cat-file -p HEAD
tree 953e0e451fdcb5c21a25ee7ef9faade5791b95ee
parent 6a28c9c996d785b716559f57149a9b5c11fd83ff
author Jakub Narebski <jnareb@xxxxxxxxx> -1280820940 +0200
committer Jakub Narebski <jnareb@xxxxxxxxx> 1280820940 +0200
git-hash-object
--
Jakub Narebski
Poland
--
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