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

Re: Transform log message during migration svn -> git (using git-svn)

From
Lars Schneider <larsxschneider@gmail.com>
Date
Jun 20, 2017, 09:32 UTC
Message-ID
<EAA4B747-FA00-4A3B-88CD-AF8EBE1F8586@gmail.com>
In-Reply-To
<8ce2bf074fcf4d6181a29eb3e7fff132@GTLBML3EX0005.bagmail.net>
Show 26 quoted lines
> On 20 Jun 2017, at 09:32, paul.mattke@s4m.com wrote:
> 
> Hi there,
> 
> this is actually not really a bug report, but much more a feature request
> (if I did not oversee an already existing feature like this):
> 
> We want to migrate our SVN repository to GIT and will be using git-svn for
> that of course. Currently in SVN, all our commit log messages start either
> with:
> 
> 123456 (a number, representing the Bug Id in our old legacy bug tracker)
> 
> or
> 
> T123456 (a number, but prefixed with T, referring a TFS item in this case)
> 
> During conversion to GIT, we want to replace the T in such log messages with
> a #, so commits, referring a TFS item will start with #123456 in the future.
> We don’t care about log messages which do not start with a T, only the
> TXXXXXX messages need to be transformed here.
> 
> I guess an operation like this is currently not possible with git-svn, isn’t
> it? So it would be nice, if a feature could be implemented that gives the
> user the possibility to specify some kind of script file for example, which
> transforms the log message in any way we want it.

You can migrate your repo from SVN to Git as is. Afterwards you can fix up the commit messages with the following command:

git filter-branch -f --msg-filter 'perl -lape "s/^T(\d+)/#\$1/"'
(this might take a while on a large repo)
- Lars
Previous: paul.mattke@s4m.comNext: paul.mattke@s4m.com
Message 2 of 6 in “Transform log message during migration svn -> git (using git-svn)”
  1. paul.mattke@s4m.comJun 20, 2017
  2. Lars SchneiderJun 20, 2017
  3. AW: Transform log message during migration svn -> git (using git-svn)paul.mattke@s4m.com, Jun 20, 2017
  4. Lars SchneiderJun 20, 2017
  5. Jeff KingJun 20, 2017
  6. Andreas HeidukJun 20, 2017

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.