"Mark E. Hamilton" wrote: > > Rondal, > <SNIP> > 2. Next, import everything from the current production area into the new > repository. This puts everything under revision control, saving all the > historical information. It also ensures you have a complete, current > backup if anything goes wrong in the next steps. Sure, it may be a lot > of irrelevant stuff, but disk space is cheap. > <SNIP>
Mark has outlined an interesting an useful method to do what I was indicating, if it was decided to keep just the latest revs in the CVS repo. After I read it, I decided that doing Mark's steps 1 through 4, would be a good idea even if the decision was to work all the history into the new repository. That is, I would do Mark's 1-4 and then in a second repository do the work of importing the histories of the files[1], and when the history imports were done, check back with the original repository to get the diff from when you set it up (and grabbed the files for making the histories), so you can patch any current changes into the new repository, then replace the 'production run directory' with a checkout from the histories repository. [1] i.e., rename foo, foo.2003-04-23, foo.2003-06-30, baz, baz.2003-04-20, baz.2003-06-15 to fo and baz in directories like: 2003-5-0/foo <-was foo.2003-04-23 2003-5-0/baz <-was baz.2003-04-20 cd 2003-5-0 cvs import crownJewels MyCompany AsWasFirstOfMay2003 cd .. 2003-7-0/foo <-was foo.2003-06-30 2003-7-0/baz <-was baz.2003-06-15 cd 2003-7-0 cvs import crownJewels MyCompany AsWasFirstOfJuly2003 cd .. current/foo current/baz cd current cvs import crownJewels MyCompany AsWasWhenIFoundThisMess cd .. Note, it has been a while since I did a set of imports, I might have the options wrong. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter _______________________________________________ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs