[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Tag made on a Branch
From: |
Karl E. Jorgensen |
Subject: |
Re: Tag made on a Branch |
Date: |
Mon, 11 Feb 2002 23:06:42 +0000 |
User-agent: |
Mutt/1.3.25i |
On Mon, Feb 11, 2002 at 02:32:53PM -0800, Paddy T wrote:
> Hi
>
> I have made a branch for one release 3.0
> The main trunk has another on going development.
> I recently made a tag on the branch with all the
> latest files.I checked out with this tag.
> Now in order to commit to the branch,I did a cvs
> update -A.
> But it fetched all latest files from the trunk into
> the working directory.Is this how it should
> behave?
This is standard behaviour.
What you probably *meant* to do was not a "update -A", but a "update
-rBranchName"
> Should I only checkout from a branch to commit
> to a branch?
Ideally: yes. But you can always get your sandbox on the correct branch
via an "update -r" (if you're prepared to risk having to sort out
conflicts).
> Or can I also checkout from a tag made on
> the branch and do cvs update -A?
Could do. But remember that update -A will bring your sandbox back on
the trunc.
Remember that you can have as many sandboxes as you want - so if you
jump back and forth between 3 branches, I'd say that you (probably) need 3
sandboxes, to avoid getting your changes mixed up. (unless you *want* to
apply & test out the same change on 3 branches...)
> Pls clarify.
> Thanks,
> Paddy Thomas
HTH
--
Karl E. Jørgensen
address@hidden
www.karl.jorgensen.com
==== Today's fortune:
Chemist who falls in acid will be tripping for weeks.
pgpYCQ2xMUncV.pgp
Description: PGP signature