[Top][All Lists]

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


From: Mark D. Baushke
Subject: Re: CVS_LOCAL_BRANCH_NUM feature
Date: Wed, 05 Mar 2003 09:16:07 -0800

Derek Robert Price <address@hidden> writes:

> Mark D. Baushke wrote:
> That's a good reason.  In fact, I might _avoid_ putting the
> configuration option in CVSROOT/config for that reason and the fact
> that I don't know nay use for CVS_LOCAL_BRANCH_NUM except CVSup.

Indeed, I have seen no other reason than CVSup for this feature.
> >A reason to keep the env variable is that there are many "HOW TO"
> >documents out there which are not getting updated very often that are
> >associated with CVSup and getting them all updated will take time. For
> >now, if folks use the cvs 1.12 sources (from cvs or after release), they
> >will be able to have a recipe that works properly with CVSup.
> >
> >It is another reason, but perhaps not as good as the first reason.
> >
> That's a reason, though I agree not as good as the first since those
> same documents will still tell users to try and apply the patch.

Right. And since they will find that their cvs sources already have the
patch, they should be fine if they follow the rest of the advise.

> Still, it shouldn't hurt to allow both an env variable and a command
> line option to set this.

Right. Having an environment variable is orthogonal to command-line

That said, it might be 'interesting' to have a way to have the .cvsrc
file use per CVSROOT settings for options. This would allow a user to
always add the CVS_LOCAL_BRANCH_NUM command-line equivalents for the
repositories that they are using that are mirrors of a master.

As I said, I think it needs more work for design and choice of command
line switches. We also need to see what code paths go thru the
RCS_magicrev() function. I think it will end up being just the 'cvs
commit' command (espeically for a new file on a branch) and the 'cvs
tag' and 'cvs rtag' commands to create the new branch in the first

        -- Mark

reply via email to

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