On Tuesday, February 11, 2003, at 10:47 PM, Olaf Hering wrote:
> On Tue, Feb 11, Wolf Josef wrote:
>>>> There was discussion on the list a while ago about having
>>>> inheritable properties. These are properties that you set on a
>>>> directory, and then anything added to that directory has those
>>>> properties added to it (including other directories, allowing
>>>> the properties to act as defaults for whole directory hierarchies.)
>>>> Would that solve your problem?
>>> Sure, that smells like 'recursive properties', if we can go that way,
>> But then there needs to be a way to specify which props should recurse
>> and which should not.
> hmm? "svn propset svn:keywords 'foo bar' ." in the root dir at revision
> 0, or any later revision.
This has all been discussed before. If you have true inheritable
properties then it is a fairly large change and is probably post-1.0.
If you go for 'cloned properties', where some properties are inherited
from their parent *at add time only*, then you get something far more
Here is the start of the earlier discussion:
In the following thread many people say they like the idea, then we get
where the idea is thrashed out in more detail... (There are also some
comments in the follow-up posts about exact property names, etc).
I have no idea how far Edward got in the implementation of this idea.
I noticed that Issue 1054
<http://subversion.tigris.org/issues/show_bug.cgi?id=1054> has been
filed for full inheritable properties, and marked post-1.0. I've added
pointers to the aforementioned posts to the issue.
Dr William Uther National ICT Australia
Phone: +61 2 9385 6926 School of Computer Science and
Email: email@example.com University of New South Wales
Jabber: firstname.lastname@example.org Sydney, Australia
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Feb 12 00:53:12 2003