From: Lawrence Mitchell <wence@gmx.li>
To: git@vger.kernel.org
Subject: Re: Rewriting references to existing commits in commit messages with filter-branch
Date: Mon, 11 Mar 2013 12:06:29 +0000 [thread overview]
Message-ID: <87haki2la2.fsf@gmx.li> (raw)
In-Reply-To: E1UF1Ag-0006m3-5k@smtp.tt-solutions.com
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?
[...]
Lawrence
--
Lawrence Mitchell <wence@gmx.li>
next prev parent reply other threads:[~2013-03-11 12:07 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 [this message]
2013-03-11 12:23 ` Vadim Zeitlin
2013-03-11 13:11 ` Thomas Rast
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=87haki2la2.fsf@gmx.li \
--to=wence@gmx.li \
--cc=git@vger.kernel.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).