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

Re: How the serevr repository is organized?

From: Magnus ... <zulutime.net_at_gmail.com>
Date: Mon, 23 Feb 2009 11:37:35 -0500

Hi Li Ma,

Let me give you some brief answers to your questions

Li Ma wrote:
> hi Martin,
> Thanks to your suggestion, I found FSVS is a very promising backup
> solution. But I do see the following problems which will prevent it from
> been adapted by enterprise user:
> 1. no UI. most of people who's not techie enough are those need help of
> a backup tools. no UI means no go to them
> 2. linux-only. unforetunately, still lots of people are using Window,
> and lots of Mac now.

That sounds like two itches that no-one has felt like scratching. If
it's a no-go, it's a no-go, and that is OK.

> 3. this is really a question: how can you delete old versions from FSVS
> or SVN? Say we have 10G of total backup already and quota of this user
> account is full. So we need to delete some copies of very old files. I'm
> not sure how FSVS can do it.

It seems you are asking for the "svn obliterate" feature. This does not
currently exist in svn. Once stuff is in the repo, it pretty much stays

Do a search on the list and issue tracker for "obliterate", and you will
find numerous discussions about this feature. I am trying to help out
with this by coming up with a well-defined functional specification
(with high-level implementation comments). However, I will not be able
to do the actual coding, so I have no idea when the feature will be

There is the option of using

and then using svnadmin load

This will strip out the first N revisions from the repo. It will NOT
work if any files have been restored ("copied from") the old revisions.
However, in a backup solution, that may not happen anyway.


Received on 2009-02-23 17:42:08 CET

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.