[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: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-05-19 22:41:27 CEST

On Thu, 19 May 2005, Marcus Rueckert wrote:

> On 2005-05-19 15:40:04 -0400, John Peacock wrote:
> > Specifically, if the inheritance is by path in the repository and you
> > copy a subtree to another place in the repository (typically as either a
> > branch or a tag) what happens to any properties which were inherited
> > (from above the copied portion) at the old location that no longer exist
> > in the new location. In this case, you can either freeze the existing
> > property values (which works well for tags but not branches) or you can
> > ignore existing inheritance (which would in general work for branches
> > but not tags). Either way, someone is going to be disappointed; there
> > are other reasons why tag vs. copy may need to eventually be two
> > different [related] operations (if only with syntactic sugar).
> >
> how about copying the required properties too?
> thats what i would expect.
OK, so I'd expect the oposite. And there is the problem. Because if I copy
a file to another location, I don't want the properties that were
previously inherited to be "frozen" for the new file just because I copied

I don't think this case shuld stop us from adding inherited properties. We
should pick a sensible default (of course my preference:-) and allow the
other to be chosen.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 19 22:32:52 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.