[Gllug] Subversion and CVS -- usable in serialized checkout/checkin model

[Christian Smith]

On Mon, 7 Feb 2005, Alan Peery wrote:

>This is probably a dead easy question.
>
>If you wanted convince developers used to the serialized "one developer
>gets the file at a time" method of development (ie Visual Source Safe),
>what commands would you show them in CVS and subversion?
>
>I remember "co" and "ci", but those commands are for the wrong system...


I'd show them:
http://svnbook.red-bean.com/
http://cvsbook.red-bean.com/

And try and teach them the benefits of the copy-modify-merge model of
source control.

Locks can be achieved in CVS using the 'cvs admin -L' to set the locking
for files to strict. To lock a strict lock file for editing, use the 'cvs
admin -l <file>' command, I believe. Files with strict locks will not
allow commits until locked with 'cvs admin -l' command, I believe. You'd
better check, as I've not tried myself.

A bit cumbersome, and I don't believe subversion even supports the model.


>
>Alan
>

Christian


-- 
    /"\
    \ /    ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
     X                           - AGAINST MS ATTACHMENTS
    / \
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug