Toward a Better Discussion of Parrot's Future VCS Options

[Jacob Helwig]

On Wed, May 5, 2010 at 05:46, Chris Fields <cjfields at illinois.edu> wrote:
>
> On May 5, 2010, at 3:54 AM, Jonathan Leto wrote:
>
>>> I want
>>> a plan for how we'll refer to revisions, and if there is a good way to save
>>> existing references to our 46286 (and counting) revisions,
>>
>> By default, when you convert a repo with git-svn, it includes
>> references to the SVN revision numbers, for instance:
>>
>> http://github.com/leto/parrot/commit/c5c01adaf92036fceb6753286581242451567e84
>>
>> This is a good reason to import with git-svn, even though it is slower
>> than svn-all-fast-export. Good thing someone keeps a daily-updated
>> git-svn mirror (thanks jhelwig++):
>>
>> http://technosorcery.net/system/parrot-git-svn.tbz
>
> Just to clarify that, the latest svn-all-fast-export (confusingly in the renamed repo svn2git on gitorious) now allows this via --add-metadata:
>
> Usage: /home/cjfields/src/svn2git/svn-all-fast-export [OPTION] [Path to subversion repo]
>
> Options:
>       --identity-map    provide map between svn username and email
>       --rules           the rules file that determines what goes where
>       --add-metadata    if passed, each git commit will have svn commit info
>       --resume-from     start importing at svn revision number
>       --max-rev         stop importing at svn revision number
>       --dry-run         don't actually write anything
>       --debug-rules     print what rule is being used for each file
>       --commit-interval if passed the cache will be flushed to git every NUMBER of commits
>    -h --help            show help
>    -v --version         show version
>
>

The "old" svn-all-fast-export" does this, too.