> -----Original Message----- > From: Andrew Jorgensen [mailto:[EMAIL PROTECTED] > Sent: Friday, January 28, 2005 13:25 > To: BYU Unix Users Group > Subject: Re: [uug] Version control software? > > > On Fri, 28 Jan 2005 11:52:51 -0700, Grant Robinson <[EMAIL PROTECTED]> wrote: >> On Jan 28, 2005, at 11:21 AM, Andrew Jorgensen wrote: >>> but unfortunately CVS doesn't even have such a thing as a >>> rename. >> >> Sure it does. >> >> ssh [EMAIL PROTECTED] >> cd $CVSROOT >> cd module_name >> mv oldfilename,v newfilename,v >> >> :) > > I hope I can trust that your :) means that you know that this > isn't a good solution... right?
It's a perfectly acceptable solution, /provided/ you don't mind not being able to track the fact that the file used to have a different name, or when the rename happened. You can also do it in CVS like this: mv $oldfilename $newfilename cvs rm $oldfilename cvs add $newfilename cvs commit -m "Renamed $oldfilename to $newfilename" but that, of course, has only the commit message to link the old file to the new one. I'll readily admit, this is a weakness of CVS, and it might be enough to make CVS unsuitable for the particular work that was asked about in this instance. That weakness doesn't, in my opinion, make up for the performance problems, Berkeley DB corruption problems, ridiculously huge disk usage on both the server and the client (yes, I know it was an intentional design decision), lack of tagging and branching (yes, I know about svn copy), global instead of per-file revision numbers (again, yes, I know it was intentional), and a host of other irritations with Subversion. -------------------- BYU Unix Users Group http://uug.byu.edu/ The opinions expressed in this message are the responsibility of their author. They are not endorsed by BYU, the BYU CS Department or BYU-UUG. ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
