[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:20 -0400

>From address@hidden  Sat Feb  3 01:59:48 2001
>Return-Path: <address@hidden>
Received: from (address@hidden [])
        by (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id 
        for <address@hidden>; Sat, 3 Feb 2001 01:59:46 +0900
Received: from localhost ([]
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OjWC-0005ih-00; Fri, 02 Feb 2001 11:57:04 -0500
Received: from [] (
        by with esmtp (Exim 3.16 #1 (Debian))
        id 14OjVe-0005iB-00
        for <address@hidden>; Fri, 02 Feb 2001 11:56:30 -0500
Received: from (aukland.YP.tgx [])
        by (8.9.3/8.9.1) with SMTP id IAA17272;
        Fri, 2 Feb 2001 08:56:27 -0800 (PST)
Received: from lima by (SMI-8.6/SMI-SVR4)
        id IAA12329; Fri, 2 Feb 2001 08:56:26 -0800
Message-Id: <address@hidden>
From: Stephen Rasku <address@hidden>
Reply-To: Stephen Rasku <address@hidden>
Subject: Re: Easiest way to move a branch to the trunk
To: address@hidden,
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: BJcGVkMFWEtUwWZbe+eYfQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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 08:56:26 -0800 (PST)
Status: O
Content-Length: 1770
Lines: 45

Brian Murrel wrote:

>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 
>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.
>I realize of course I could use "cvs update -j" to move it all over
>but that is going to create a boatload of conflicts.  I can deal with
>conflicts easily (and tediously) enough but I wonder why I should 
>to bother.  It seems that I should be able to simply replace the
>contents of the main branch with the development branch in an easier
>way, no?
>All suggestions welcome, thanx.

I know that this is shutting the barn door after the horses have gone 
but your new development should have been on the trunk and you should 
have had stable branch.  Since the new development is already on the 
head this removes the need to merge (or put) new development there.

However, to solve your current problem you will have to write a 
script.  Assuming that you have a workspace already checked out on the 
head, this is how you put the branch version of a file to the head:

        cvs update -p -r branch-tag foo.c > foo.c
You will have to iterate this over every file in the tree.  Once all 
the files are updated you can check in the whole repository.

Stephen Rasku                   E-mail: address@hidden
Senior Software Engineer        Web:
TGI Technologies

Info-cvs mailing list

reply via email to

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