[bt-devel] mercurial repo

[Sveinung Kvilhaugsvik]

> this is only testing and I will delete the repo later.
Great to see that you are testing distributed version control systems.
Have you considered if you should change some of the data in your
history when/if you switch over for real?

An example on what projects often do when they switch from SVN to a
distributed version control systems is to change the way the
committers are identified from svn user names to the form "full name
<email at example.com>" for their svn history as well as future commits.
The advantages of using the standard way to identify the committer for
all history is that the data becomes more usable for various third
party tools. (There are tools that can automatically review copyright
based on VCS history, webservices that let you look at what a
committer does no matter what project he commits to, etc) The down
side is that you strictly speaking are changing history.

If you use fastexport from svn and then fastimport to the DVCS you
import to (bazaar, git and I think also mercury supports this) you can
make this kind of changes automatically when you import by putting a
script between the export and the import. (Instead of
"fast-export-software | fast-import-software" you do
"fast-export-software | change-history | fast-import-software")

Sveinung