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

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

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Mar 11, 2013, 13:53 UTC
Message-ID
<513DE1E8.7010302@alum.mit.edu>
In-Reply-To
<E1UF1Ag-0006m3-5k@smtp.tt-solutions.com>
On 03/11/2013 12:45 PM, Vadim Zeitlin wrote:
Show 6 quoted lines
> [...]
>  The first thing I'd like to do is to replace all references to subversion
> revision numbers in the commit messages with the corresponding git commit
> SHA1s. [...] I have a couple of dozens of errors which happen
> because the file .git-rewrite/map/$commit doesn't exist yet when I'm trying
> to look it up.

The quick and dirty solution would be to rewrite your script such that if the commit is still unknown to Git, it emits a warning and leaves the commit message unchanged (i.e., leaves the Subversion revision number untouched). Then simply run the filter-branch a few times until it emits no warnings.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Vadim ZeitlinNext: Vadim Zeitlin
Message 6 of 7 in “Rewriting references to existing commits in commit messages with filter-branch”
  1. Vadim ZeitlinMar 11, 2013
  2. Lawrence MitchellMar 11, 2013
  3. Vadim ZeitlinMar 11, 2013
  4. Thomas RastMar 11, 2013
  5. Vadim ZeitlinMar 11, 2013
  6. Michael HaggertyMar 11, 2013
  7. Vadim ZeitlinMar 11, 2013

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.