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

Re: tsvn:logwidth in svn repository (Re: svn commit: r12696 - trunk/subversion/po)

From: John Peacock <jpeacock_at_rowman.com>
Date: 2005-01-14 13:44:58 CET

Branko Čibej wrote:
> What do you do with switched files whose "true" parents have a different
> prop value?

I'm not sure I know for sure what you are referring to here. Are you talking
about a mixed rev WC where the inherited property changed between revs on some
files? If you are using inherited properties, there is going to have to be more
use of 'svn up' to stay consistent.

Or are you talking about 'svn switch' to move a file from another branch (or
e.g. external) into a working copy. The external case is easier because the
inherited properties are associated with containing directory, so that falls
directly out since we don't support external links to files (yet). In the
switch case, I hadn't thought of that since I've only used switch in the context
of at least a directory (if not a tree).

What I've been thinking about is that the inherited property on the WC is a
property of the parent directory that a file is located in; hence mixed revs or
switched files only see the inherited property for the directory they are
located in right now. In the repository, however, the inherited properties are
merely a composite of all properties in the decomposition of the repository
local path (no complicated dual inheritance). In that respect, the only edge
case is what to do about branches (where you may want the inheritance to float)
vs tags (where you would definitely want the properties to be frozen). Those
cases are going to have to be dealt with by a commandline option and which is
the default is up in the air (I'm leaning towards copying the inherited
properties to any copied subtree as the default).

> Don't forget compatibility with generic DAV clients.

Hrm. If the server cannot determine that it is deal with a generic DAV client,
then that limits us to always populating the files as if they had the property
and worrying about inheritance only on the server. I suspect this would
actually be easier to code overall, but it would certainly be less efficient.

> You don't need a new table for _versioned_ inherited props, but you do
> need one for unversioned inherited props -- i.e., ACLs.

I thought you said that ACLs and inherited props were different things. ;)


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 14 13:46:50 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.