Re: Need help for migration from CVS to git in one go (ie, FORGETTING CVS history)

From: Jakub Narebski <jnareb@gmail.com>
Date: Nov 6, 2008, 03:08 UTC
Message-ID: <m3zlkdeelm.fsf@localhost.localdomain>
In-Reply-To: <200811060014.57046.fg@one2team.net>

Francis Galiegue <fg@one2team.net> writes:

Show 7 quoted lines

> Since my first email where I said that we wanted to migrate from CVS to a 
> distributed SCM, we have had a lot of discussions with developers and my 
> chief (which happens to be a developer too). We have come to the following 
> conclusions:
> 
> * git has credentials (heck, it "runs" the Linux kernel, Wine,
>   Samba, and other);

The main contenders among top OSS version control systems seems to be Git, Mercurial and Bazaar-NG for distributed SCM, and Subversion for centralized SCM.

> * the "distributed" part of it is indeed an advantage (planned
>   developments with huge technical/functional impacts);

> * 52 CVS modules, fine; but then this can become one and 52
>   subdirectories in them and still act as separate modules from
>   the build system point of view (which I have implemented, so
>   I can change it);

I think that those CVS modules should become separate repositories, perhaps joined together using submodules. This is one of more difficult things during conversion.

Note that in Git commits are always whole tree (whole project) commits.

Show 6 quoted lines

> * second: even though this may be a "non problem", we use Bonsai,
> which has the ability to see what was commited by whom, given a time
> interval (from d1 to d2): the base gitweb allows to search by
> commiter, which is good, but it has no date boundaries: do tools
> exist for git that can do this? If not, that wouldn't be a big deal,
> however...

First, there are more web interfaces than gitweb, see http://git.or.cz/gitweb/InterfacesFrontendsAndTools

Second, you can do this from command line, using combination of commit limiting a..b and a...b, or --since=<date> or --after=<date> and --before=<date>, commit message searching --author, --committer, and --grep, and path limiting "git log -- <pathspec>".

Third, it would be not that hard to add more advanced search support to gitweb; this is even one of planned features.

Show 5 quoted lines

> * third: also Bonsai-related; Bonsai can link to Bugzilla by
> matching (wild guess) /\b(?:#?)(\d+)\b/ and transforming this into
> http://your.bugzilla.fqdn.here/show_bug.cgi?id=$1. Does gitweb have
> this built-in? (haven't looked yet) Is this planned, or has it been
> discussed and been considered not worth the hassle?

This is (under name of 'committags') in gitweb TODO; gitweb-xmms2 support this IIRC or supported this (for Mantis and not Bugzilla though...)

-- 
Jakub Narebski
Poland
ShadeHawk on #git