[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDUxNl0gIHN2biBvYmxpdGVyYXRl?=
From:       kbenton () tigris ! org
Date:       2006-09-30 21:59:42
Message-ID: 20060930215942.18418.qmail () tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=516






------- Additional comments from kbenton@tigris.org Sat Sep 30 14:59:40 -0700 2006 -------
FYI all - as a Perforce administrator, the ability to obliterate is not just a
convenience, it's a requirement.  As repositories grow over time (ours grows at
a logarithmicly increasing rate, currently about 50GB / year), at some point, it
makes sense to archive certain parts of the repository.  That's not possible
unless there's a way to dump certain parts of the repository, then obliterate it
from the production space.  If the old information is needed, reference back to
the archive is made.

The problem we have is that as repositories grow, performance is negatively
impacted.  If there's no way to remove obsolete information from a production
repository, it becomes bloated at best and useless at worst.  I understand that
there is a request to take this discussion to the lists, however, I feel it's
important to report that the lack of an obliterate function is making it
difficult for my company to justify switching to Subversion.

It's been said (above) that there's no question that an Obliterate function is
useful.  The question is, when is someone going to move things from being "nice
to have" to making obliterate a requirement for Subversion?  I would hope that
it's implemented prior to the next release (1.5 or 2.0).

Use cases:
1) Removal of confidential information
2) Removal of obsolete information
3) Removal of tags, branches, or trees that have moved to other repositories.


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]