Re: Rename strange/unexpected behavior.

"Arthur Barrett" <arthur.barrett-qn/[email protected]> Mon, 24 Jan 2011 22:21:14 +1100
Newsgroups gmane.comp.version-control.cvs.tortoisecvs.user
Message-ID <[email protected]>
Gordo,
 
Your report is not very helpful - but well meaning.
 
TortoiseCVS 10.10 was released over 2 years ago in January 2009, and
contained a CVSNT build from July 2008!  
 
Yes there were bugs, they were fixed years ago.
 
Please keep your software up to date, and never ever bother reporting
bugs in ancient software to volunteers.
 
If you can reproduce the bug using the latest release of TortoiseCVS
with the latest CVSNT server, please drop us another note.
 
Regards,
 
 
Arthur Barrett
Product Manager - CVSNT
 

	-----Original Message-----
	From: [email protected] [mailto:[email protected]] 
	Sent: Monday, 24 January 2011 4:49 AM
	To: tortoisecvs-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
	Subject: [TortoiseCVS] Rename strange/unexpected behavior.
	
	

	 

	With TCVS version 1.10.10 on Windows XP Pro, SP3.

	I understand the Rename command remains "in development"... I am
posting so that the development team will be aware of some strange and
unexpected behavior.

	 

	My repository contains several modules. One of these is the
collection of files that represent a web site. It became necessary to
rename a number (about 25) of files from XXXX.html to XXXX.shtml.

	 

	I chose to use the TCVS "Rename" command...  for the first time.

	 

	In all but 2 of the cases the rename appeared to work as
intended... CVSNT ran without error, the name was changed in the
sandbox, and was "marked" as being locally modified.

	 

	For two of the files the name was changed... But, in each case,
the file was marked as being NEWLY added (marked with a ?).
Investigation showed that the file was, in fact, NEW, and the revision
history of the original files appears to be gone! (update, for instance,
did not add the old file back to the sandbox).

	 

	Running a "commit" on the containing directory (the top level
directory) generated an error - citing these two files. I subsequently
"add"ed  and "commit"ted these two files individually. A subsequent
"commit" on the directory generated a log of every directory in the
module... but did not actually "commit" any of the renamed files.

	 

	A "Refresh Folder Status" on the top level directory, marked all
of the "renamed" files as up-to-date.

	 

	But, finally, the top level directory is marked as "locally
changed" (no contained files at ANY directory level are so marked), and
a "commit" shows one of the "messed up" renamed files, but doesn't
really do a commit... i.e. no revision change.

	 

	Oh, and I appear to have picked up a sticky tag on one of the
second level directories... 

	 

	I will be happy for any advice on how to get the sandbox back to
a "stable", "up-to-date" state and get rid of the new sticky tag.

	 

	Hope that this information helps the development of a reliable
rename command.

	 

	Gordo

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d

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