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

List:       subversion-dev
Subject:    Re: Enhancement: Deprecating Paths
From:       David Waite <mass () akuma ! org>
Date:       2004-06-22 22:55:15
Message-ID: 39A1DEA9-C49F-11D8-B8AD-000A95C89D86 () akuma ! org
[Download RAW message or body]

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

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