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

RE: Best practices on how to reorganize repository

From: Dieter Oberkofler <d.1234567890_at_qualiant.at>
Date: Fri, 28 Mar 2008 19:08:32 +0100

1) It is quite a large project by itself (the trunk has about 50000 files)
2) We have converted almost 15 years of history into SVN (about 30000
revisions)
3) We also have quite some binary data in the repository (documentation,
tools, images, etc)
4) A very large number of tags and branches have been used
5) A large number of quite large vendors branches are part of the repository

-----Original Message-----
From: Henrik Sundberg [mailto:storangen_at_gmail.com]
Sent: Friday, March 28, 2008 13:50
To: users_at_subversion.tigris.org
Subject: Re: Best practices on how to reorganize repository

2008/3/28, Dieter Oberkofler <d.1234567890_at_qualiant.at>:
> Our SVN repository is growing very quickly and we are starting to have
> problems with the backup of the fully repository and would therefore
> like to reduce it in size by reorganizing it. What are the best
> practices (in order of importance) to:
> 1) Physically remove branches and tags that are no longer needed?
> 2) Physically remove removed files (that should never have been in
> the repository in the first place)?
> 3) Physically remove old history revisions?
> Thank you,
> Dieter

Not answering your question..., but can you tell us why the repository is
growing so fast?
/$

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-28 19:07:49 CET

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.