Johannes Schindelin wrote:
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.
I'm still struggling a bit to understand ref specs. I'm using --all at
the moment, but that's very slow. What I need is to filter the new
commits of all branches. Will origin@{1}..origin do that, or does
it just affect master?
P.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
