I plan on doing the same thing (move our repo) by:
1. writing a script that changes CVS/Repository files
2. having users change their own CVSROOT environment variables if they don't use
the global shell init script
3. giving users the choice of running the script or rechecking out everything
(of course, I'll give them a deadline for when stuff /must/ be checked back in)
Noel
[EMAIL PROTECTED] on 2000.05.26 03:19:41
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: Moving repository: best way to handle this?
I have to move our repository from a mchine to another and in the same time
I'll switch to server mode. This is on NT so symbolic links tricks won't
help...
What's the best and easiest way to do this given that a numer of users are
working on projects and have files checked out?
Should I:
1) write a script which fixes all the refs to the old repository in the
Repository files (plus fix their CVSROOT)?
or
2) have them either commit or forget about their current changes, remove
their working copy and checkout from the new repository?
Can anyone share experience in doing that?
Thanks,
D.
------------------------------------
Dominique de Waleffe
Mission Critical
Tel: + 32 2 757 10 15
Email: [EMAIL PROTECTED]
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.
