From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to set git commit timestamp
Date: Tue, 08 May 2007 03:54:38 +0200 [thread overview]
Message-ID: <f1ol0d$tcd$1@sea.gmane.org> (raw)
In-Reply-To: 20070508013833.GB11311@spearce.org
Shawn O. Pearce wrote:
> Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
>> söndag 06 maj 2007 skrev Guido Ostkamp:
>>> I am writing a tool to convert from another SCM to git and need to replay
>>> all checkins. I know how to set the log message and the author, but there
>>> appears to be no command option for the timestamp (Mercurial for example,
>>> has a 'hg commit -d date <file>' syntax for this).
>>
>> If you are writing a converter then you should really use the plumbing
>> commands rather than porcelains like git-commit and in particular you should
>> look at git-fast-import for a really fast methord of importing (and packing)
>> objects.
>
> As the author of a few convert-to-git things, fast-import really
> is the easiest way to import stuff into git, even if it doesn't
> need to be "fast". The input format is quite simple to create,
> and is documented pretty heavily in the git-fast-import manual page.
>
> There's also contrib/fast-import/import-tars.pl which handles
> decompressing and importing one or more tar files into a Git
> repository. Works pretty well...
By the way, is there fast-import version of git-quiltimport?
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-05-08 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 16:03 How to set git commit timestamp Guido Ostkamp
2007-05-06 16:41 ` Alex Riesen
2007-05-06 17:26 ` René Scharfe
2007-05-06 19:51 ` Robin Rosenberg
2007-05-08 1:38 ` Shawn O. Pearce
2007-05-08 1:54 ` Jakub Narebski [this message]
2007-05-08 1:57 ` Shawn O. Pearce
2007-05-08 11:29 ` Johannes Schindelin
2007-05-11 10:58 ` Jakub Narebski
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='f1ol0d$tcd$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.