Removing data from subversion

[Ahtesham Kazi <ah...@gmail.com>]

Greetings,

I have read that subversion does not allow deleting obsolete not required
data.
Is there a way we can fork from some point onwards ?


-- 
regards,
Ehteshaam

Re: Removing data from subversion

[Thorsten Schöning <ts...@am-soft.de>]

Guten Tag Ahtesham Kazi,
am Mittwoch, 28. November 2018 um 05:12 schrieben Sie:

> I have read that subversion does not allow deleting obsolete not required data.
> Is there a way we can fork from some point onwards ?

You can dump a range of revisions from an existing repo and create a
new one based on the dump:

> dump: usage: svnadmin dump REPOS_PATH [-r LOWER[:UPPER] [--incremental]]
> load: usage: svnadmin load REPOS_PATH

If you really want to use the entire history before some revision,
this is pretty easy and safe and you don't need to deal with
difficulties by excluding things.

Carefully read the help regarding how "load" behaves for UUIDs and
think about the existing repo, it's checked out working copies etc.
Safest would be to start with a new UUID in the new repo and new
checkouts.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: Removing data from subversion

[Nico Kadel-Garcia <nk...@gmail.com>]

On Wed, Nov 28, 2018 at 6:42 AM Ahtesham Kazi <ah...@gmail.com> wrote:
>
> Greetings,
>
> I have read that subversion does not allow deleting obsolete not required data.
> Is there a way we can fork from some point onwards ?

Kind-of sort-of. There's a lot of discussion in the Red Book and
mailing list. To prune content, you'll be committed to switching to a
new Buversion repository. Pruning in place is *dangerous*, it's one of
the oldest requested features, and as best I can tell it's never going
to happen.

The fastest and simplest is to snapshot a working copy of the limited
content that you want and make a new repository, with no history. That
is least likely to include bulky content from commits that touched
multiple branches. Second fastest, if your Subversion content is not
complex or heavily dependent on svn: settings, is to use git-svn to
import the desired branch and only the desired branch, apply "git gc
--aggressive" to the git repo, and use "git-svn" to export it back up
to an entirely new Subversion repository. This works surprisingly
well, though it can get quite confused about "svn:keywords" and
similar attributes.

The trickiest is to do a dump, exclude, and reload into a new
repository. That's better able to preserve the history, unsullied,
with really good provenance of subtle tuning like "svn:keywords". But
I've personally given up on the approach. Subversion is aimed at
conserving history, and the history of embedding bulky content
accidentally or embedding keywords or embarrassing software errors
accidentally and very reasonably wanting them *out* of the repos is
why I've used the other approaches.

Re: Removing data from subversion

[Juan Gabriel Covas <jg...@softline.es>]

You could svn export the desired revision to start with, and then make an initial commit to a new repo

Regards,

Juan

Enviado desde BlueMail<http://www.bluemail.me/r?b=14063>
En 28 nov. 2018, en 12:44, Ahtesham Kazi <ah...@gmail.com>> escribió:
Greetings,

I have read that subversion does not allow deleting obsolete not required data.
Is there a way we can fork from some point onwards ?