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

Re: Inherited properties document

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2005-05-19 19:25:55 CEST

On Thu, 2005-05-19 at 12:43 -0400, John Peacock wrote:
> Greg Hudson wrote:
> > So I'll outline a poor man's alternative.
> So this is a write-once scheme; you only copy the auto-props under
> limited circumstances during initial creation. Anyone wanting to alter
> the autoprops later is stuck with walking the tree and making largescale
> changes to the repository. It's also a narrow targeted solution where a
> wider scope would solve many problems.

Correct; thus the "poor man's" modifier.

> Would you have less objection to inherited properties if we limited it
> strictly to single container inheritance?

I don't really object to inherited properties; I just have some doubts
that we can get to the point of having a design which (a) we can
implement, and (b) doesn't commonly bite users with edge cases.

To answer your question: while it's much, much simpler to inherit only
from parent directory to file, I think it solves the part of the problem
people mostly don't care about. All of the use cases I can think of for
inherited properties involve wanting to set a directory property which
applies to a whole tree of directories (auto-props for files, ignores,
log template if we go that route).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 19 19:27:46 2005

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.