[cvsnt] cvs edit - something changed ?

[Eric Nicholson]

I've seen Tortoise edit/unedit badly often.  Especially in the case where
the timestamp on a file has changed, but the contents haven't.  In this case
Tortoise doesn't know to unedit the file, and won't even give you the option
to later.  Sometimes the icons then get out of sync and the checkout
statuses are messed up until I straighten it out with the commandline.
Which reminds me, I was going to mention this on the Tortoise list, but I
couldn't subscribe,  time to try again.

Regards,
Eric

-----Original Message-----
From: Torsten Martinsen [mailto:torsten at tiscali.dk]
Sent: Tuesday, March 09, 2004 8:54 AM
To: Martin Cole
Cc: cvsnt at cvsnt.org
Subject: Re: [cvsnt] cvs edit - something changed ?


Martin Cole wrote:

>I wonder if something has changed with "cvs edit" recently.
>
>Using tortoise, I usually right click in the module folder and select "cvs
edit" and it previously would "edit" the files that were watched (not all
were watched) and after commiting, I would right click and send "cvs
unedit".
>  
>
That has never been the intention. "cvs commit" removes the edit on the 
file, so you do not have to do "cvs unedit" (except if the file has not 
actually changed, in which case "cvs commit" will do nothing).

>With tortoise 1.6.6 / cvsnt 2.0.34 it seems that it breaks when doing this
(previously I was using tort 1.6.2 / cvsnt 2.0.11) also when the unedit
breaks, all the unwatched files become read-only.
>
If a file becomes read-only, it is because there is a watch set on it.

-Torsten
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt