git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Joel C. Salomon" <joelcsalomon@gmail.com>, git@vger.kernel.org
Subject: Re: Back-dating commits--way back--for constitution.git
Date: Tue, 3 Aug 2010 10:00:52 +0200	[thread overview]
Message-ID: <201008031000.53581.jnareb@gmail.com> (raw)
In-Reply-To: <201008030939.09999.jnareb@gmail.com>

Dnia wtorek 3. sierpnia 2010 09:39, Jakub Narebski napisał:
> Dnia wtorek 3. sierpnia 2010 00:47, Junio C Hamano napisał:
> > Jakub Narebski <jnareb@gmail.com> 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@gmail.com>
  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@gmail.com> -1280820940 +0200
  committer Jakub Narebski <jnareb@gmail.com> 1280820940 +0200
  
  git-hash-object

-- 
Jakub Narebski
Poland

  reply	other threads:[~2010-08-03  8:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-02 18:32 Back-dating commits--way back--for constitution.git Joel C. Salomon
2010-08-02 18:34 ` Shawn O. Pearce
2010-08-02 18:41   ` Joel C. Salomon
2010-08-02 21:25 ` Ævar Arnfjörð Bjarmason
2010-08-04 16:38   ` Joel C. Salomon
2010-08-04 19:07     ` Ævar Arnfjörð Bjarmason
2010-08-05 21:37     ` Joel C. Salomon
2010-08-05 21:58       ` Ævar Arnfjörð Bjarmason
2010-08-05 22:10         ` Sverre Rabbelier
2010-08-06  8:18           ` Jakub Narebski
2010-08-06 14:01             ` Michael Witten
2010-08-06 15:08             ` Sverre Rabbelier
2010-08-06 15:18         ` Joel C. Salomon
2010-08-06 15:19           ` Ævar Arnfjörð Bjarmason
2010-08-06 15:29             ` Joel C. Salomon
2010-08-06 16:00             ` Brandon Casey
2010-08-06 16:50               ` Ævar Arnfjörð Bjarmason
2010-08-06 16:44           ` Brandon Casey
2010-08-08  3:46             ` Joel C. Salomon
2010-08-08  4:11               ` Joshua Juran
2010-08-02 21:48 ` Jakub Narebski
2010-08-02 22:47   ` Junio C Hamano
2010-08-03  7:39     ` Jakub Narebski
2010-08-03  8:00       ` Jakub Narebski [this message]
2010-08-03  8:55   ` Michael J Gruber
2010-08-03  9:32     ` Joshua Juran
2010-08-03 12:44       ` Jeff King
2010-08-03 17:37         ` Joshua Juran
2010-08-03 17:49           ` Jeff King
2010-08-03 10:02     ` Jakub Narebski
2010-08-03 10:08       ` Jakub Narebski
2010-08-03 12:48       ` Jeff King
2010-08-03 13:19         ` Jakub Narebski
2010-08-03 13:20           ` Jeff King
2010-08-03 13:24             ` Michael J Gruber
2010-08-03 13:32               ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008031000.53581.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=joelcsalomon@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).