[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: Nathan Fiedler <nfiedler_at_bluemarsh.com>
Date: 2003-01-15 07:46:21 CET

This is really quite unnecessary. I've been using Subversion actively
for exactly nine months (with 805 revisions) and have had no problems at
all. Even the occassional database format change merely requires a
simple dump/load procedure. With hot-backup.py you are covered in terms
of backups.

Trust me, save yourself the effort and just use Subversion as-is.


P.S. I am not a member of the Subversion team, so I do not speak for

On Tue, 2003-01-14 at 17:20, Alexander L. Belikoff wrote:
> Hello everyone -
> I'm fairly new to SVN but I'm vey impressed. It alreqady looks really good.
> I'd like to switch my home repository from CVS to SVN, but being paranoid as I
> am, I'd feel much better knowing that my commits are backed up in CVS. Yes, I
> know that no data loss has happened for quite some time, but still, I'd like
> to play it safe. And I'm pretty sure that a lot of people out there would
> have more incentive to start using SVN having such a feature.
> The easiest way to provide such a backup is via a post-commit hook. This will
> not handle branching/merging but considering it is for an emergency backup
> only, we could live with this shortcoming. I'm going to write a tool for
> doing just that but before I start, a couple questions:
> 1. Has anyone already written such a tool? It would be a shame to duplicate
> the effort...
> 2. I cannot find any information on how to manage hooks. Where can I find some
> info on how to add/remove/list hooks?
> Thanks in advance,

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 15 07:47:05 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.