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

Re: RFC: Log Message Templates via new hook.

From: John Peacock <jpeacock_at_rowman.com>
Date: 2005-05-20 17:44:16 CEST

Michael Sinz wrote:
> See, the problem is a "tag" should copy all of the properties as
> I want the tag to be a "frozen in time marker" yet certain branches
> (not normal, but pre-release branches) I don't want the properties
> copied, or at least not some of them. This is where the whole iprops
> thing gets to be hairy. All properties need to be copied some of the
> time but not all of the time. But some properties need to be copied
> all of the time (mime-type, needs-lock, etc)

 From the discussion so far, it certainly seems to me like the kinds of
properties that you are talking about copying are the kinds of
properties that are likely to be repository defaults (or at the very
least project defaults). In other words, the properties likely to be
important to maintain are going to be higher in the tree (and hence
inherited anyways); anything else can be set manually (or through the
use of a post-commit hook).

I was thinking about this on the drive to work this morning and it
occurs to me that a simple inheritance/no copy model probably gets us
very far without introducing any big suprises along the way. What I am
suggesting is that iprops are strictly based on the path within the
repository; copying a directory node from one location to another does
not copy any inherited properties (though if there are iprops associated
with the actual directory being copied, those would of course be copied).

For example, think of this tree:

/ - repository root, contains iprops for svn:mime-types
     and any other repository-wide properties; all directories
     below inherit them (though they can also override).

/project2 - all overrides to the above, plus any project specific
     additional properties (this is where custom keyword definitions
     would probably live). For example svn:ignore might be project

/project1/branches - each of these three could have individual
     overrides of the above, as well as additional custom props. If
     a different log-template was used for tags or branches, that
     would be stored in the parent directory those subtrees.

The only time you would have to worry about setting iprops is if you
copied a directory outside of its original subtree, so it would no
longer be under the original inherited properties.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 17:49:31 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.