[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WinCVS 1.10 problem Logging in

From: Eric Siegerman
Subject: Re: WinCVS 1.10 problem Logging in
Date: Tue, 16 Jul 2002 00:39:49 -0400
User-agent: Mutt/1.2.5i

On Mon, Jul 15, 2002 at 09:13:32PM -0700, Mike Ayers wrote:
>       If I edit the file CVS/Root for a given working directory, are there 
> any other 
> dependencies to be aware of, or is this just like setting the CVSROOT env 
> var, 
> except with a higher priority?

Yes to the latter, therefore no to the former.  It's safe, and
indeed the usual method for dealing with such situations.  There
might even be a script in contrib to automate it...

>       Could I delete the CVS directory tree in a given working directory, 
> then `cvs 
> login` to a different (or the same) server to correctly rebuild the CVS 
> directory tree, pointing to the new server?


If you're lucky, CVS will just refuse to create the "CVS"
subdirectory.  If you're unlucky, it'll go ahead and do it.  Why
"unlucky?"  Because it'll get it wrong, and you won't notice till
later.  The likelihood of CVS getting it right is pretty small
(depending on how active your repo is, how up-to-date your
sandbox was before you started, etc.)

You'll lose all sorts of other state that you really wanted to
keep, such as sticky tags/dates, the revision that each file was
last synced with (losing this will completely bollix future
updates/merges/commits) -- all the stuff that CVS is about in the
first place.  That state info is stored nowhere else, so if you
trash it, CVS can't possibly recreate it.

Just edit CVS/Root, either manually or with a script at your


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
Anyone who swims with the current will reach the big music steamship;
whoever swims against the current will perhaps reach the source.
        - Paul Schneider-Esleben

reply via email to

[Prev in Thread] Current Thread [Next in Thread]