[Top][All Lists]

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

Re: Committing files that were tagged (sticky tags)?

From: Larry Jones
Subject: Re: Committing files that were tagged (sticky tags)?
Date: Thu, 11 Apr 2002 16:14:08 -0400 (EDT)

Danial Islam writes:
> When I do a  "cvs co -r Release1 myModule",
> I can't check-in any files that I modified from it, it says the sticky
> tag is not on a branch.
> How would someone be able to checkin from a tagged part of the stream?
> Or would I have to create a branch from Release1 and then have them
> checkin to this branch and merge to the MAIN stream from there?

It's not clear what you want to do.  If you want to keep track of bug
fixes to Release1, then you need to create a branch to do that and merge
any fixes that need to go into the current release to the trunk.  If you
just want to fix a bug that was first found in Release1 in the current
release, you can make the change to the files that you checked out in
Release1, test it, then do "cvs update -A" to update to the current
revision (which will merge your changes) and then commit.  You should
probably read the chapter on branching and merging in the manual:


-Larry Jones

I've got PLENTY of common sense!  I just choose to ignore it. -- Calvin

reply via email to

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