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

Re: Restricting access to old revisions of a project?

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 3 Feb 2012 13:05:30 -0500

On Fri, Feb 3, 2012 at 12:47 PM, Ryan Schmidt
<subversion-2012a_at_ryandesign.com> wrote:
> On Feb 3, 2012, at 06:14, Chris Evans wrote:
>> I've had a request to restrict access to revisions of certain SVN projects in a repository older than a set revision number. My repo is accessed via Apache HTTPS. Has anybody had any experience of this or would know where to start? I'm guessing it could be possible in the httpd config to deny access if the http request contains the revision, but I'm not sure what modules or config would allow this. Any help would be greatly appreciated.
> Sorry, this is not a feature Subversion offers.

The simplest method is to do an export/import to a new repository. and
start your history from scratch with that new repository. Leaving a
README.txt in place that points to the old versions would allow
authorized personnel to obtain the old erversions.

This *would* break your change history, and does nothing for any
svnsync maintained repositories people may have had. Related issues
have come up before with large binary objects accidentally stored in
Subversion, and confidential data accidentally stored in source
Received on 2012-02-03 19:06:05 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.