[Top][All Lists]

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

(no subject)

From: root
Subject: (no subject)
Date: Mon, 13 Aug 2001 05:06:31 -0400

>From address@hidden  Sat Feb  3 07:00:43 2001
>Return-Path: <address@hidden>
Received: from ( [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Sat, 3 Feb 2001 07:00:41 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OoCX-0006wt-00; Fri, 02 Feb 2001 16:57:05 -0500
Received: from ([])
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OoAL-0006sn-00
        for <address@hidden>; Fri, 02 Feb 2001 16:54:49 -0500
Received: from [] by 
with ESMTP
  (SMTPD32-6.05) id ACCE338200F0; Fri, 02 Feb 2001 15:55:26 -0600
Received: from cobbe by with local (Exim 3.12 #1 (Debian))
        id 14OoCz-0000VH-00; Fri, 02 Feb 2001 15:57:33 -0600
From: Richard Cobbe <address@hidden>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <address@hidden>
  "Brian J. Murrell" <address@hidden>
Cc: address@hidden
Subject: Re: Easiest way to move a branch to the trunk
In-Reply-To: <address@hidden>
References: <address@hidden>
X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
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: <>,
List-Id: Announcements and discussions for the CVS version control system 
List-Unsubscribe: <>,
List-Archive: <>
Date: Fri, 2 Feb 2001 15:57:33 -0600 (CST)
Status: O
Content-Length: 1734
Lines: 45

Lo, on Friday, February 2, Brian J. Murrell did write:

> I have a project/repository which has a main branch (trunk) for
> stable, released versions and a development branch.  The development
> branch was branched off of the main branch a while ago for development
> and has going along gangbusters.  Now it is time to release.  What is
> the easiest way to move the develoment branch onto the main branch so
> that what is on the main branch is completely replaced by the
> development branch.

We're about to have to do this at work ourselves, because the folks who
created the branch didn't really understand what they were doing, and so
got the trunk & branch backwards.  (New development has been on the

If you tagged the trunk at the point where you branched, then this should
actually be pretty easy.  Call the tag PRE-BRANCH-TAG:

* Get a working copy on the trunk; make sure there are no uncommitted

* If you want to preserve that line of development, you may want to tag and
  branch here.

* Back on the trunk, roll back all changes made since the branch:
    cvs update -j HEAD -j PRE-BRANCH-TAG

* Resolve any conflicts, although I'd suspect that there wouldn't be any.
  You may also want to commit here, but that's up to you.

    to incorporate all changes made on the development branch.  Again,
    there shouldn't be any conflicts.

* commit.

If you *don't* have PRE-BRANCH-TAG, then you're up a creek, and you'll have
to go with one of the other more labor-intensive suggestions posted.


Info-cvs mailing list

reply via email to

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