[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion with CVS "backup"?

From: Alexander L. Belikoff <abel_at_vallinor4.com>
Date: 2003-01-15 04:51:21 CET

On Tuesday 14 January 2003 22:09, Eric Gillespie wrote:
> "Alexander L. Belikoff" <abel@vallinor4.com> 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

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?
2. What commands are safe to be called from post-commit hooks? Is 'svn cat'

> > Yes, I know that no data loss has happened for quite some time,
> You mean never.

I stand corrected. :-)

Alexander L. Belikoff                      GPG f/pr: 0D58 A804 1AB1 4CD8 8DA9
Bloomberg L.P.                                       424B A86E CD0D 8424 2701
abel *at* vallinor4 *dot* com             (http://pgp5.ai.mit.edu for the
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 15 04:51:53 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.