From: Felix Eckhofer <felix@tribut.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Passing rev-list options in git-filter-branch broken
Date: Sun, 29 Jun 2014 16:00:49 +0200 [thread overview]
Message-ID: <cacf17948e270ab33cc9ff145c4a1af7@tribut.de> (raw)
In-Reply-To: <xmqq1tua2oi5.fsf@gitster.dls.corp.google.com>
Junio,
thanks for your reply and your patch.
Am 27.06.2014 20:31, schrieb Junio C Hamano:
> [...]
> would be a better workaround that would not break repositories with
> large number of references, but it obviously will lose --date-order
> option (why would it be even necessary, though? I suspect that
> forcing the date-order will make the resulting pack a lot worse by
> robbing the data stream of locality).
We're migrating some svn repositories to git. The use case is to replace
mentions of svn revisions in commit messages by the corresponding commit
hash. Therefore, the commits must be ordered by svn revision number,
which is not guaranteed for commits on different branches with
--topo-order.
Regards
felix
prev parent reply other threads:[~2014-06-29 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 16:26 Passing rev-list options in git-filter-branch broken Felix Eckhofer
2014-06-27 18:31 ` Junio C Hamano
2014-06-27 22:20 ` Junio C Hamano
2014-06-29 14:00 ` Felix Eckhofer [this message]
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=cacf17948e270ab33cc9ff145c4a1af7@tribut.de \
--to=felix@tribut.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).