Re: Rewriting references to existing commits in commit messages with filter-branch

From: Vadim Zeitlin <vz-git@zeitlins.org>
Date: Mar 11, 2013, 12:23 UTC
Message-ID: <loom.20130311T131746-169@post.gmane.org>
In-Reply-To: <87haki2la2.fsf@gmx.li>

Lawrence Mitchell <wence <at> gmx.li> writes:

Show 8 quoted lines

> Vadim Zeitlin wrote:
> 
> [...]
> 
> > git filter-branch --msg-filter svnmsg2git --tag-name-filter cat -- --all
> 
> git rev-list lists by default in chronological order.  Do you
> want to pass --topo-order as one of the rev-list options?

 Thanks, this looked like a good idea but reading git-filter-branch code it
seems to already do it, at
https://github.com/git/git/blob/master/git-filter-branch.sh#L269 you can see
that it does "git rev-list --reverse --topo-order ...".

 So this probably won't help (I could try it just in case I'm missing something
but the first errors appear after almost 2 hours of running...). Notice that I
could well be wrong in my explanation of what happens, perhaps it's not related
to the order of processing of the branches/trunk at all. All I know is that when
a chronologically later commit referring to preceding one on a different branch
is processed by git-filter-branch, sometimes (or perhaps even always) the file
corresponding to the previous commit is not yet present in .git-rewrite/map
directory.

 Thanks again for any help with this,
VZ