"Alexander L. Belikoff (by way of Alexander L. Belikoff )" wrote:
> On Tuesday 14 January 2003 22:09, Eric Gillespie wrote:
> > "Alexander L. Belikoff" <firstname.lastname@example.org> writes:
> > > I'd feel much better knowing that my commits are backed up in
> > > CVS.
> > How is hot-backup.py insufficient?
> Hmm... I shouldn't have used the work backup. 'Contingency plan' is much more
> appropriate in this situation. Which also explains exactly why hot-backup.py
> is not enough. I have no problem with backing up the repository myself. The
> tool I'm looking for is for the "shit hits the fan, SVN is dead, and I
> desperately need my revisions NOW!" kind of situation. Plus it is supposed to
> give me a worm fuzzy feeling about the fact that my worked is also backed by
> the system that has already been time-proven, let alone the fact that CVS is
> about RCS format and in case CVS is dead as well, I can still deal with ,v
Well, I'm guessing you'll probably find a lot of resistance to this
idea, as it looks like Subversion going backwards :) One of the key
aspects that CVS doesn't manage are file and directory renames that
Subversion does handle. There may be more that I can't think of
There are probably better ways of handling the case if svn is dead
and you want to get to the repository, such as .tar.bz2 backups of
the working copy at each revision.
> Anyway, I've started writing the tool and it's painful. :-) But I'll get it
> to some logical point and will submit to the list.
> Still a couple questions though:
> 1. How do I register/manage hooks?
Just copy the appropriate *.tmpl script in the hooks directory to the
same name without the .tmpl and edit to suit your needs. Check the
sample scripts out.
> 2. What commands are safe to be called from post-commit hooks? Is 'svn cat'
After a post-commit, you should be able to call any program.
Blair Zajac <email@example.com>
Plots of your system's performance - http://www.orcaware.com/orca/
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Jan 15 05:02:03 2003