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

Re: Enhancement: Deprecating Paths

From: David Waite <mass_at_akuma.org>
Date: 2004-06-23 00:55:15 CEST

You can also just create your own local structure policy, such as 'move
deprecated code to /deprecated/', although moving the deprecated code
might not be what you want to do.

-David Waite

On Jun 22, 2004, at 4:45 PM, Dominic Anello wrote:

> On 2004-06-21 12:18:17 +0200, kraythe@arcor.de wrote:
>> It would be great if an admin could mark a path as deprecated. This
>> would allow people to check out and browse the path but not commit to
>> that path. In projects where old code is migrated or deprecated, this
>> would be great.
>
> If you are using mod_authz_svn you can put a section that looks like
> the
> following in your access file:
>
> [/deprecated/path]
> * = r
>
> That will mark the path read-only. Otherwise, you can use a pre-commit
> hook to accomplish the same thing (reject the transaction if it
> includes anything in the deprecated path).
>
> -Dominic

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 23 00:56:03 2004

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.