Once upon a time we started with a project and CVS. This project then
evolved and is now two projects; one that is residing in HEAD and one in
another branch. We both release versions and both have branches to keep
track of these. This is getting silly...
So, we have this *huge* respository with in essence two branches in it.
How, if at all possible, can I split this into two different CVS
repositories while still keeping the history?
I realise that the best way would be to just dump the branch and use
that as a base for the new repository. I have advocated that the
developers on that side could well use our repository for history while
working in the new, but that has met with some resistance. Thus the need
for a split with retained history.
One way would be to use the small script I saw posted here once that
saved all revisions of a file. I could thus extract all versions of all
files and then add them one at a time to the repository, but this is
getting silly as well...
Any ideas, anybody?
Cheers!
Karl-Koenig Koenigsson
--
HADZOR (n.)
A sharp instument placed in the washing-up bowl which makes it easier to cut
yourself.
(The Meaning of Liff, Douglas Adams)
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
- Re: Splitting a respository Karl-K�nig K�nigsson
- Re: Splitting a respository Fabian Cenedese
