4

We have a CVS repo with many years of history. It has become huge and unwieldly, so we would like to split this singe repo in to two repos:

  1. The main repo would have 1 year's worth of history, up to and including present day. This is where all dev work would take place.
  2. An archive repo would have the complete history, up to the point where the main repo would take over. This would be read-only, and only used to look at historical changes.

Given that we are starting with one huge, monolithic CVS repo, is it possible to split it up in this way? How can this be accomplished?

John Dibling
  • 719

1 Answers1

1

I would suggest the following strategy :

  • Copy the repository to the archive machine (lots of info available - example)
  • Remove/outdate the old revisions (again lots of info available - info1, info2).
    You should study with great caution the "-o" admin parameter in the Reference Manual for your CVS product.

Verifying the stripped-down repository won't be simple, maybe by exporting everything before and after and diffing to see if you have everything.

Negative remark : It might be time to buy a new and faster computer.

harrymc
  • 498,455