GIT and Github - howto.

[Matt Graham]

From: keith smith <klsmith2020 at yahoo.com>
> Thanks James.  What is everyone else doing[?]  I'm sure others have
> had the problem of needing to "check out" code so others cannot
> modify the file.

Lock->modify->check in->unlock is the old way, dude.  You can *do* that using
SVN, but you're discouraged from doing so repeatedly in the documentation. 
Apparently, now you're supposed to grab everything, modify things, then merge,
handling conflicts/breakage via your brain.  This makes it easier to modify
parts of a huge project.  (It can create problems for small projects with few
developers, but who cares about those projects, anyway?)  Note that these
problems were also present in older things like CVS, but CVS is very infra dig
now because it's so annoying to move/rename things in CVS.

If you *need* exclusive locking, git is the wrong source-code versioning
system to use.  But as Alan said, you probably don't need exclusive locking as
much as you think.

-- 
Matt G / Dances With Crows
The Crow202 Blog:  http://crow202.org/wordpress/
There is no Darkness in Eternity/But only Light too dim for us to see