(no subject)

[root]

>From address@hidden  Sun Feb  4 01:17:49 2001
>Return-Path: <address@hidden>
Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164])
        by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
BAA02875
        for <address@hidden>; Sun, 4 Feb 2001 01:17:47 +0900
Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org)
        by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
        id 14P5CP-0000Cm-00; Sat, 03 Feb 2001 11:06:05 -0500
Received: from verano.sba.ca.us ([204.144.244.103])
        by fencepost.gnu.org with esmtp (Exim 3.16 #1 (Debian))
        id 14P59w-00009W-00
        for <address@hidden>; Sat, 03 Feb 2001 11:03:33 -0500
Received: from verano.sba.ca.us (address@hidden [127.0.0.1])
        by verano.sba.ca.us (8.8.7/8.8.7) with ESMTP id JAA04229;
        Sat, 3 Feb 2001 09:08:01 -0700
Message-Id: <address@hidden>
X-Mailer: exmh version 2.0.2
To: Dorthe Luebbert <address@hidden>
Cc: address@hidden
Subject: Re: Turning a branch into a new branch 
In-Reply-To: Your message of "Sat, 03 Feb 2001 11:57:36 +0100."
             <address@hidden> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Pierre Asselin <address@hidden>
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Id: Announcements and discussions for the CVS version control system 
<info-cvs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Archive: <http://mail.gnu.org/pipermail/info-cvs/>
Date: Sat, 03 Feb 2001 09:08:01 -0700
Status: O
Content-Length: 1510
Lines: 41


> 1. I checked out branch VERSION-A
> 2. I modified some files locally
> 3. I want to create from the these files VERSION-B
> 
> CVS asks me to commit the modified files first. But I would commit them
> to VERSION-A, though they should not exist in VERSION A.

General procedure to start a new branch as an afterthought:

    $ cvs tag VERSION-B-bp     : tag the starting point
    $ cvs tag -b VERSION-B     : create the branch
    $ cvs update -rVERSION-B   : get on the branch
    $ cvs commit               : commit pending changes to the branch

The first command places the tag `VERSION-B-bp' on the revision you
checked out (i.e. before your changes).  It's for future reference only.

The second command starts a branch off of the same revision, still before
your changes.

The third command "puts you on the branch".  This consists of two actions:
1)  It merges the pending changes in your sandbox with all the changes that
    have occurred on branch `VERSION-B';  the branch is empty, so this is a
    vacuous merge.  Your sandbox files don't really change.
2)  It plants a sticky tag for `VERSION-B' in your sandbox's administrative
    files.

The fourth command commits your changes.  Because of the sticky tag, the
commit goes to VERSION-B.  Use `cvs update -A' to stop working on the branch
and return to the trunk.

-- 
Pierre Asselin
Westminster, Colorado


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs