[Top][All Lists]

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

Re: Argh... cvs admin -b

From: Eric Siegerman
Subject: Re: Argh... cvs admin -b
Date: Fri, 14 Sep 2001 17:00:32 -0400
User-agent: Mutt/1.2.5i

On Fri, Sep 14, 2001 at 12:59:58PM -0700, Josh Baudhuin wrote:
> Argh... whenever you check something into the main trunk, after having
> marked the default branch, the default branch setting in the archive
> file gets lost.
> Is this expected behavior? Is it a bug?

I don't believe CVS has ever been intended to cope with people
setting arbitrary default branches at the RCS level.  The
behaviour in this situation is presumably undefined (and thus the
specific behaviour you're seeing is neither expected, nor
unexpected, nor correct, nor a bug :-)

CVS itself uses the RCS default branch for exactly one thing,
"cvs import".  If you use it for anything else, you're on your

The manual says (node "admin options"):
> There is one reason to run `cvs admin -b': to revert to the
> vendor's version when using vendor branches (*note Reverting
> local changes::).

Perhaps that should be strengthened to "...only one reason...".


|  | /\
|-_|/  >   Eric Siegerman, Toronto, Ont.        address@hidden
|  |  /
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea.
        - RFC 1925 (quoting an unnamed source)

reply via email to

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