From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sun, 10 Feb 2008 12:51:59 GMT
Subject: Re: All I wanted was git-fast-export
Message-ID: <alpine.LSU.1.00.0802101248260.11591@racer.site>
In-Reply-To: <47AECCDC.3050500@glidos.net>

Hi,

[please do not look the other way when you respond to me, i.e. do not cull 
me from the Cc: list.  Thankyouverymuch]

On Sun, 10 Feb 2008, Paul Gardiner wrote:

> Johannes Schindelin wrote:
> 
> > The thing is, filter-branch was _written for this purpose_.  So if you 
> > know what commit you rewrote last, you can make the process 
> > faster/safer by issuing
> > 
> > 	$ git filter-branch --msg-filter="<blabla>" <old-commit>..master
> 
> That does look just what I need, but did you see the reason I thought I 
> couldn't use it? I need to repeatedly sync the git repository from a 
> live cvs repository, and repeatedly filter the new commit messages.

Oh, I thought you saw why I put in that "<old-commit>...".  You do not 
really need it, as filter-branch will come up with the _same_ commit 
hashes, unless _something_ was changed.

IOW if you have only commits without that "Summary: " prefix, the 
filter-branch call will be a (not so cheap) no-op.

But of course, I meant to suggest (admittedly, in a very short short-hand) 
that you use "git filter-branch ... origin@{1}..origin" after cvsimport.

Hth,
Dscho