--- Paul Sander <[EMAIL PROTECTED]> wrote: > Hmmm... Let's recap: > > >> cp $1 $2 > >> cvs rm -f $1 > >> cvs add $2 > >> cvs commit -m "moved $1 to $2" $1 $2 > > Where is the *location of the RCS file* recorded in > the comment? > Sure, the wrapper could read the CVS meta-data, but > that's proprietary > to CVS and therefore not guaranteed to remain > compatible in future > releases.
Not only this, but it breaks the "One checkin per change set" rule if there happens to be multiple renames in a change set (unless, of course, you want to start creating micro change sets). Keeping this info within comments is a hack as we all should know by now for at least a couple of reasons: 1. Users have no place within the tool to describe why they made such a change. 2. The information is internal to CVS so any wrapper would break if CVS's internals would need to change. Noel __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
