From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Joel C. Salomon" <joelcsalomon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Back-dating commits--way back--for constitution.git
Date: Mon, 2 Aug 2010 11:34:20 -0700 [thread overview]
Message-ID: <20100802183420.GN25268@spearce.org> (raw)
In-Reply-To: <i372v0$3np$1@dough.gmane.org>
"Joel C. Salomon" <joelcsalomon@gmail.com> wrote:
> I'd figured to play with Git in an unusual way: to create a repository
> for the U.S. Constitution where amendments are presented as patches.
> E.g., instead of the First Amendment being placed at the end (as is
> usual) I'm putting it in Article 1, Section 9 (Limitations of Congress).
> Proposed amendments get branches, which get merged in later.
>
> But I'm trying to get the dates right, and I'm missing something. For
> example, I made the initial commit with the line
>
> $ git commit --author="The Philadelphia Convention <>" \
> --date="Mon, 17 Sep 1787 12:00:00 EST"
>
> but that's not actually setting the commit date to 1787.
>
> Am I doing something wrong, or is Git (quite reasonably) unable to
> accept commit dates that far in the past?
Its probably running into problems with time_t on your system being a
32 bit value, and thus having trouble going before some time in 1901.
--
Shawn.
next prev parent reply other threads:[~2010-08-02 18:34 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 [this message]
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
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=20100802183420.GN25268@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--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).