Is there an advantage to using --no-metadata in git svn clone?

I'm doing a one-way convert from an SVN repository to a Git repository using git svn clone. Most examples do this with the --no-metadata flag - is there an advantage to using this flag?

I understand that the flag removes the SVN revision numbers. I can think of reasons why it may be useful to keep these around (such as referring back to specific commits mentioned in bug tracking software).

What are the arguments for using the --no-metadata flag? Is there any benefit other than a sensation of breaking all ties?

Answers


It is actually not recommended:

This option is NOT recommended as it makes it difficult to track down old references to SVN revision numbers in existing documentation, bug reports and archives. If you plan to eventually migrate from SVN to git and are certain about dropping SVN history, consider git-filter-branch(1) instead. filter-branch also allows reformatting of metadata for ease-of-reading and rewriting authorship info for non-"svn.authorsFile" users.


Need Your Help

Different Bubble Sort algorithm codes - what's the difference? C++

c++ bubble-sort

I've come across many different implementations of the Bubble sort algorithm in C++. I'll list a few now (just the few lines that are different of each other) so someone can tell me the difference....

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.