Re: unexpected behavior with tag -> move

Thank you for your response, Torsten.
 
I have done some more research and I understand your point that this a
server side (CVSNT 2.5.03) issue and not really a TortoiseCVS issue.
 
Relative to your reply, no offence was taken.... I will simply say that I
had read the documentation on TAGS -- in the Tortoise and CVSNT
documentation (which I reread this morning) plus a couple of books on the
use of CVS. I am always interested to learn and would accept any reading
suggestions you may have. Let me just say that none of this documentation
says anything about this kind of behavior. And, one is clearly lead to
believe that "move" means "move" and nothing more.
 
Having said that and with all due respect, I understand (and accept) all of
the admonitions on the use of this command -- this was one of those rare
cases where a tag move was appropriate...  please let me make the following
points: the word "move" means move, not move some AND create or add others;
one can't "move" something that doesn't exist; If one "shouldn't move tags
around", why offer the command?
 
The -H description of  the CVSNT -F option is very clear: "-F      Move tag
if it already exists."  (underline is mine)
 
Running a few command line tests, it seems clear that the -F option has NO
EFFECT on how CVSNT responds.
 
 
Thanks again for your reply. I will not make this mistake again (it took me
several hours of work to recover from it). I still say that better
documentation would save others from stumbling into this.
 
Gordo
 
 

-----Original Message-----
From: Torsten Martinsen [mailto:[email protected]] 
Sent: Friday, February 05, 2010 17:48
To: [email protected]
Cc: tortoisecvs-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [TortoiseCVS] unexpected behavior with tag -> move


[email protected] wrote: 

I have a module with many files. A relatively small subset of them (about
1/3) are tagged for a particular release. Recently I made a change to most
of the set of tagged files and needed to "move" the existing tag to the
newest version....  I selected the highest folder and did a "move existing
tag" command.
 
Much to my horror, tortoisecvs actually BOTH moved the existing tag on the
changed files AND "created" the tag on every other file in every other
folder in the module!
 
Is this the way it is supposed to work?   If so, please put some sort of
warning in the dialog box.

Yes, this is how CVS is designed. There will not be a warning - TortoiseCVS
has no way to determine that the tag is set on some files and not on others.


 
So, now I have EVERY file in the module tagged as being part of this
release.... Any suggestions on how to proceed?

Not to offend, but I think you need to read up on how tags work. You do not
usually move tags around (among other reasons, there is no way to undo a tag
move).

-Torsten


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4839 (20100205) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

_______________________________________________
tortoisecvs-users mailing list
tortoisecvs-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/tortoisecvs-users