[nimh-dev] Source control

["Jon Stewart" <stew1@xxxxxxxxxxx>]

Here's documentation for Subversion:

	http://svnbook.red-bean.com/en/1.1/svn-book.html

I showed it off to Tom a bit last night. I've talked about it with Joel.

My home linux box, martial.homedns.org, is a 900MHz Duron running 
Slackware 10. It is a fairly secure box, and ssh is the only way in.

Subversion comes with a lightweight server which supports ssh tunneling. 
So, with proper ssh authentication, you can gain access to the repository 
on martial from anywhere.

So, to check out a local working copy of the nimh repository, you need 
only execute, e.g.:

	svn checkout svn+ssh://tom@xxxxxxxxxxxxxxxxxxx/home/dev/nimh

Once you create your working copy, you should not have to specify the 
above URL. Subversion keeps all kinds of data hidden away in .svn 
directories (including a full copy of the latest HEAD revision, so you can 
diff locally; "svn diff -r HEAD" diffs against the remote repository).

Subversion projects are supposed to be organized into three top-level 
directories, trunk, tags, and branches. Until we get close to releasing, 
we shouldn't have to worry too much about branching, and probably not even 
tagging. So, trunk/ effectively acts as the source root.

If you do a checkout now, you'll see that scan.py is sitting in trunk all 
by its lonesome.

To commit changes, you need to specify a message. I usually do this inline 
using the -m option, but you can also create a detailed message with an 
editor. If you are out-of-date with the repository, i.e. someone else has 
checked in changes in the meantime, your commit will be rejected. You will 
have to do an update. This policy means that we're always working against 
head and not performing stale check-ins.

Commits are atomic and numbered. You can revert to an older version of the 
repository using svn update and specifying the changeset number. No wanky 
date/time calculations.


Jon
-- 
Jon Stewart                                 Advanced Los Angeles C++
stew1@xxxxxxxxxxx                           http://www.alacpp.org
_______________________________________________
nimh-dev mailing list
nimh-dev@xxxxxxxxxxx
http://lists.ellipsis.cx/mailman/listinfo/nimh-dev