git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Passing rev-list options in git-filter-branch broken

From
FEFelix Eckhofer <felix@tribut.de>
Date
Jun 29, 2014, 14:00 UTC
Message-ID
<cacf17948e270ab33cc9ff145c4a1af7@tribut.de>
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:
Show 6 quoted lines
> [...]
> 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

Previous: Junio C Hamano
Message 4 of 4 in “Passing rev-list options in git-filter-branch broken”
  1. Felix EckhoferJun 27, 2014
  2. Junio C HamanoJun 27, 2014
  3. Junio C HamanoJun 27, 2014
  4. Felix EckhoferJun 29, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.