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

Re: hot-backup question

From: Robert Dailey <rcdailey_at_gmail.com>
Date: Fri, 29 Aug 2008 11:04:28 -0500

On Fri, Aug 29, 2008 at 10:44 AM, Robert Dailey <rcdailey_at_gmail.com> wrote:
> HI,
> I'm currently running hot-backup on my repository. However, I noticed
> that it will create multiple backups for the same revision. Is it
> possible for it to not do this? For example, if
> myrepository-200.tar.gz already exists, it should not make a
> myrepository-200-1.tar.gz. It will continue to append -# where # is a
> number 1 and up.
> Help is appreciated.

I found this comment in the hot-backup.py file:

# If there is already a backup of this revision, then append the
# next highest increment to the path. We still need to do a backup
# because the repository might have changed despite no new revision
# having been created. We find the highest increment and add one
# rather than start from 1 and increment because the starting
# increments may have already been removed due to num_backups.

How can the repository change without the revision number increasing?
Are the changes important enough to have to create a new backup? It
would be great if this comment went into more detail.

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-08-29 18:04:49 CEST

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

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