[Top][All Lists]

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

Re: Exact branching date?

From: S I
Subject: Re: Exact branching date?
Date: Mon, 18 Jul 2005 14:12:01 -0700

Thank you for your help.  It worked. :)

----Original Message Follows----
From: Jim Hyslop <address@hidden>
To: S I <address@hidden>
CC: address@hidden
Subject: Re: Exact branching date?
Date: Mon, 18 Jul 2005 15:26:32 -0400
MIME-Version: 1.0
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.211); Mon, 18 Jul 2005 12:26:37 -0700 Received: from [] ([]) by (InterMail vM. 201-253-122-130-110-20040306) with ESMTP id <address@hidden>; Mon, 18 Jul 2005 15:26:37 -0400
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: DreamPossible Inc.
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
References: <address@hidden>
Return-Path: address@hidden
X-OriginalArrivalTime: 18 Jul 2005 19:26:38.0037 (UTC) FILETIME=[9E01D050:01C58BCE]

S I wrote:
Hi Jim

I'm going to branch today too. Our last build off of Main came to a halt this weekend due to our release. I have not continued to build off of the mainline, nor branched yet.

I just want to rule out the possibility of any errors. Please tell me if I'm on the right track.

I'm going to do a complete clean check out of the last build based on its label by

C:\>cvs co -r build99 proj1
C:\>cd proj1
C:\>cvs tag -R -b branch99

Will this ensure that build100 will be the next build off of Main and branch99 is my current release?

That will work, yes. For checking in updates, you have to make sure that developers check out the correct version, of course, by specifying either

cvs [co or update] -r branch99 proj1 # to update the current release


cvs co proj1 # for a fresh checkout
cvs update -A proj1 # to update an existing checkout


reply via email to

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