Re: importing cvs logical modules

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: May 25, 2006, 06:16 UTC
Message-ID: <46a038f90605242316l4b0a0963m638f7a2e47936000@mail.gmail.com>
In-Reply-To: <93c3eada0605242302x24ca1272xd7bfc3a677b32845@mail.gmail.com>

On 5/25/06, Geoff Russell <geoffrey.russell@gmail.com> wrote:

Show 5 quoted lines

> The tight linkage is absolutely essential.
>
> When we tag the system, we
> want to tag everything (not individually tag all 300 programs)
> so that later we can to branch at that tag. Very few of our

Then you want a single git repo/tree/project. The thing is how to work through your mangled CVS history.

Two options there...

 - Don't. Import from after the last directory reorg or from your last
interesting release. Keep the cvs tree for people who really want to
dig into the past. this has several advantages, as initial checkouts
will be faster, import times shorter, less pain overall.

 - Mangle import to match your reorganizations:
   - Generate the cvsps output file
   - Duplicate/copy files in the cvs repo so that files are in both
places if you've been mving them around.
   - Mangle the cvsps output file from each reorg onwards. This is
nasty, but it will define the history that cvsimport sees.

cheers,

martin