Title: branch removal question
I
asked this question last Friday but got no response.
Was it
poorly asked, not enough information, too
ignorant for words? If I need to supply more
information
please
let me know, I would be glad to.
Thanks,
Don
Butts
-Original Message
Don Butts wrote:
> I asked this question last Friday but got no response.
> Was it poorly asked, not enough information, too ignorant for
> words?
How about, this requires a few more brain cycles than were available at the
time? :=)
> -Original Message-
> We are using cvs in s
> Don Butts wrote:
>
> Content-Type: multipart/mixed; boundary="===1243246784=="
Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!
> We are using cvs in somewhat of a non-standard way.
> We have a production cut of our compiled source t
Normally one would apply a tag to the versions that are ready for testing,
and update the tag as bugs are fixed. Then apply a second tag to the
code that reaches production quality. To apply the second tag, use the
"cvs rtag -r" option.
The bummer with this is that if you make bug fixes in your
>--- Forwarded mail from [EMAIL PROTECTED]
>Don Butts wrote:
>> I asked this question last Friday but got no response.
>> Was it poorly asked, not enough information, too ignorant for
>> words?
>I wouldn't remove the branches. I'm always reluctant to remove anything from
>the history.
>Instead
[EMAIL PROTECTED] wrote:
> Floating tags can also be used. For example, create a tag
> called PRODUCTION and apply it to the next release. Then
> just run "cvs update"
> in the production area, and the proper versions will appear.
Yep, that's basically the idea I was trying to get across.
> Th
