From: Thomas Rast <trast@student.ethz.ch>
To: Vadim Zeitlin <vz-git@zeitlins.org>
Cc: <git@vger.kernel.org>
Subject: Re: Rewriting references to existing commits in commit messages with filter-branch
Date: Mon, 11 Mar 2013 14:11:14 +0100 [thread overview]
Message-ID: <87y5dut72l.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <loom.20130311T131746-169@post.gmane.org> (Vadim Zeitlin's message of "Mon, 11 Mar 2013 12:23:45 +0000 (UTC)")
Vadim Zeitlin <vz-git@zeitlins.org> writes:
> Lawrence Mitchell <wence <at> gmx.li> writes:
>
>> 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 ...".
Try overring that with --date-order (you may have to patch the source).
--topo-order doesn't order by dates. --date-order does somewhat
(respecting topology), which in the absence of clock skew should do what
you are looking for.
Note that you cannot *remove* --topo-order and use the default, which is
to only respect dates and not topology; that would break filter-branch.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-03-11 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 11:45 Rewriting references to existing commits in commit messages with filter-branch Vadim Zeitlin
2013-03-11 12:06 ` Lawrence Mitchell
2013-03-11 12:23 ` Vadim Zeitlin
2013-03-11 13:11 ` Thomas Rast [this message]
2013-03-11 15:58 ` Vadim Zeitlin
2013-03-11 13:53 ` Michael Haggerty
2013-03-11 14:05 ` Vadim Zeitlin
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=87y5dut72l.fsf@pctrast.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=vz-git@zeitlins.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).