Larry Jones <[EMAIL PROTECTED]> wrote:
> Pierre Asselin writes:
> >
> > Yes, it is routine. You can even use RCS and CVS at the same time
> > on the same project, they will mostly ignore one another.
> That's not quite true. It's perfectly safe to use both to *read* files,
> but you can lose changes if you use both to update the same file at the
> same time because they don't use the same locking mechanism.
Good grief, not like that ! I mean using RCS in a sandbox, behind
CVS' back.
sandbox> mkdir RCS
sandbox> ci -l sandboxfile
sandbox> cvs update sandboxfile
sandbox> ci -l sandboxfile
sandbox> cvs commit sandboxfile
stuff like that. It never occurred to me to run RCS commands on
$CVSROOT/path/sandboxfile,v because my $CVSROOT is usually remote.
Using RCS that way is a little like creating a private branch in CVS,
but more lightweight --and less organized. I do that when I am making
intricate changes, I want the option to backtrack, and I don't want
to commit broken code to CVS.
--
pa at panix dot com
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
