How to set git commit timestamp

How to set git commit timestamp

[Guido Ostkamp]

Hello,

does somebody know a method to specify a timestamp for a 'git commit'?

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).

Any help is appreciated.

Regards

Guido

Re: How to set git commit timestamp

[Alex Riesen]

Guido Ostkamp, Sun, May 06, 2007 18:03:14 +0200:
> 
> does somebody know a method to specify a timestamp for a 'git commit'?
> 

Set GIT_AUTHOR_DATE (and maybe GIT_COMMITTER_DATE) in the environment.

Re: How to set git commit timestamp

[René Scharfe]

Guido Ostkamp schrieb:
> Hello,
> 
> does somebody know a method to specify a timestamp for a 'git commit'?
> 
> 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).

You can use the environment variable GIT_COMMITTER_DATE to force a
specific commit date.  Please see the man page of git-commit-tree for
(some) more info.

René

Re: How to set git commit timestamp

[Robin Rosenberg]

söndag 06 maj 2007 skrev Guido Ostkamp:
> Hello,
> 
> does somebody know a method to specify a timestamp for a 'git commit'?
> 
> 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.

-- robin

Re: How to set git commit timestamp

[Shawn O. Pearce]

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...

So I agree with Robin, give fast-import a try.

-- 
Shawn.

Re: How to set git commit timestamp

[Jakub Narebski]

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

Re: How to set git commit timestamp

[Shawn O. Pearce]

Jakub Narebski <jnareb@gmail.com> wrote:
> By the way, is there fast-import version of git-quiltimport?

No, and I don't think its easy.  Isn't a quilt patchstack stored
as a series of patch files?  So "importing" it into Git requires
applying the patch to the base tree, then writing that base tree
to the ODB.  fast-import doesn't know how to run git-apply, though
Junio and I did kick it around (generally) a few months ago on #git.

-- 
Shawn.

Re: How to set git commit timestamp

[Johannes Schindelin]

Hi,

On Mon, 7 May 2007, Shawn O. Pearce wrote:

> Jakub Narebski <jnareb@gmail.com> wrote:
> > By the way, is there fast-import version of git-quiltimport?
> 
> No, and I don't think its easy.  Isn't a quilt patchstack stored as a 
> series of patch files?  So "importing" it into Git requires applying the 
> patch to the base tree, then writing that base tree to the ODB.  
> fast-import doesn't know how to run git-apply, though Junio and I did 
> kick it around (generally) a few months ago on #git.

You'd have to pretend that all of these patches are branches. Well, in the 
end they are...

Ciao,
Dscho

Re: How to set git commit timestamp

[Jakub Narebski]

On Tue, 8 May 2007, Johannes Schindelin wrote: 
> On Mon, 7 May 2007, Shawn O. Pearce wrote:
>> Jakub Narebski <jnareb@gmail.com> wrote:

>>> By the way, is there fast-import version of git-quiltimport?
>> 
>> No, and I don't think its easy.  Isn't a quilt patchstack stored as a 
>> series of patch files?  So "importing" it into Git requires applying the 
>> patch to the base tree, then writing that base tree to the ODB.  
>> fast-import doesn't know how to run git-apply, though Junio and I did 
>> kick it around (generally) a few months ago on #git.
> 
> You'd have to pretend that all of these patches are branches. Well, in the 
> end they are...

Or rather that patch _series_ are branches. 

It would be also nice to have one of the patch management UI on top of git
like StGIT or Guilt (IIRC pg is no longer maintained) to import series
of patches as unapplied from Quilt (or from mbox/file).

-- 
Jakub Narebski
Poland