Workflow: split repository?

[Jan Wielemaker <wielemak@science.uva.nl>]

Hi,

I've got a big active project, until yesterday managed using CVS. As
with any distributed academic research project the repository has become
a nice mess where most files are in the wrong place and there are
several almost independent sub-projects living in directories.

The plan is/was to

	* Convert everything to GIT (done, through cvs2svn)
	* Everyone keeps hacking on their bits, while one is starting
	to reorganise the structure by moving files and directories
	and changing import headers, and other file references in
	a GIT branch.
	* Now we merge the continued work and the reorganisation to
	end up with a nice clean hierarchy :-)
	* Split the big project into multiple projects.  One of the
	reasons is that we want to make part of them public.  Others
	we cannot publish as they contain copyrighted data.  I understand
	we can reunite them using GIT sub modules.

Does this make sense?

While splitting we want to *loose* history information for some of the
projects.  That is easy: simply create a new repository from the current
files.  For some however we would like to *preserve* the history.  This
means we would like to pick a hierarchy with its history.  After quite
a bit of reading, I get the impression this cannot be done.  Am I right?

Is the only way to create a GIT repositiory right away from a subset of
the CVS for which we want to preserve the history?

	Thanks --- Jan