Martin Jørgensen wrote with a bogus address:
Hi,
Since I'm most used to tortoiseCVS but also would like to learn the
command line, I didn't yet found out what's the best way of seeing which
files are new/modified before commiting them, so you can also add
whatever isn't already added.
Is cvs update absolutely safe in that, it doesn't overwriting anything
newer? Because I think that would do the trick...
It may merge with something newer (but already CVS committed) in your sand
box, but it never overwrites data it has not controlled (i.e., has been
committed).
I'm just a bit paranoid if it some day overwrites my new files with cvs
update, before I commited them...
No, it should be safe. You should not have any files overwritten, you should
get a "move away xyz; it is in the way"
http://lists.gnu.org/archive/html/info-cvs/2001-03/msg00281.html
http://lists.gnu.org/archive/html/info-cvs/2001-03/msg00169.html
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
_______________________________________________
info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
