[Top][All Lists]

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

RE: cannot committ ... sticky tags

From: Teala Spitzbarth
Subject: RE: cannot committ ... sticky tags
Date: Tue, 8 Jan 2002 14:48:44 -0800


You said in your email yesterday that *you* created the 
Release_Aug21_2001 tag.  

The only way *you* can have a working copy of the tree
listing sticky tags of Release_Aug21_2001 is if *you*
either 1) did a fresh "cvs co -r Release_Aug21_2001 <module-name>"
to create your tree or 2) did an update "cvs up -r Release_Aug21_2001" 
within your tree.  Nothing anyone else did elsewhere in the CVS
repository has affected whether *you* have sticky tags in your working

Either you did one of these commands and forgot, or annoying developers
have crept onto your machine and sullied this working directory with
an update to the Release_Aug21_2001 tag.  

CVS will not allow you to create a branch with the same name as a tag
that already exists on a given file.   Try it, CVS will complain and
error out.  You're spinning in circles because you are thinking this
particular work tree wasn't pulled or updated to the Release_Aug21_2001
tag, but it was, and you need to clear it with update -A

Running update -A is not going to affect the status of that
Release_Aug21_2001 tag back in the repository it *only affects the files
in your working copy*.

Do re-read the chapters on tags, sticky tags and branches - it will save
you from ineffective conjecture.....


-----Original Message-----
From: Schwenk, Jeanie [mailto:address@hidden
Sent: Tuesday, January 08, 2002 10:07 AM
To: CVSpost (E-mail)
Subject: RE: cannot committ ... sticky tags

Thanks everyone for their responses but I need some additional

1)  I checked out all my files prior to the vendors putting the sticky
on.  So why are the sticky tags effecting me?  Is it because commit
that the selected files are up to date with the current revision in the
repository?  It doesn't make sense that it would be looking at the
tags ... doesn't it compare with the trunk from where I originally

2)  removing the sticky tags (cvs update -A), does not effect the sticky
tags in the repository just in my local copy?

3)  Do I need to worry about any conflicts because there is a tag and a
sticky tag with identical names?  It must not have given the vendors any
warning but it just doesn't seem right to have a tag for release with
same name as a branch tag.


Info-cvs mailing list

reply via email to

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