[nimh-dev] repository

["Jon Stewart" <stew1@xxxxxxxxxxx>]

I had an old repository containing some other stuff I've been working on. 
Since subversion does not keep track of changeset numbers on a 
project-by-project basis, I decided it would be better to set up a 
separate repository for our work, to keep changeset numbers 
contiguous/ordinal.

I didn't tell Tom this, though, so he checked in his changes to the old 
repository. I've taken his mods and checked them into the new repo. I've 
also changed the permissions on the old repo so that this won't happen 
again by accident. So, all's good.

One thing, be sure not to checkin build artifacts (e.g. *.pyc). I'll 
investigate to see whether we can tell svn to ignore such files.

The repository to use is:

  svn+ssh://martial.homedns.org/home/dev/nimh

Also, if the repository ever gets corrupted (I've had it happen to me by 
cancelling an operation mid-course), don't worry. The repository is just a 
berkeley db, so it's fully journaled. I just have to issue a recover 
command as root (I haven't been able to figure out why I need to be root 
to do this, but it doesn't work otherwise...).


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