[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: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-05-21 18:20:31 CEST

Michael Sinz wrote:
> John Peacock wrote:
> > Michael Sinz wrote:
> > > 1) When I make a branch (the pre-release lock-down branch)
> > > I want to have the template be different (include manager signoff
> > > or bug ticket requirement). But the branch was created by svn cp
> > > from another branch/trunk which had a different template. How
> > > does this work? [To me this gets back to the fact that svn really
> > > needs to know the difference between "cp" and "branch" and "tag"
> > > even if they are mostly not different.]
> >
> > I can see a couple of ways that this could be accomplished; it really
> > depends on how you have your repository organized:
> >
> > a) Standard project/trunk, project/branch, project/tag format - in this
> > case, you would set a log-template iprop on trunk and branch; any
> > branches would inherit the special branch template immediately upon
> > copying (I'm assuming the trivial path-based inheritance).
[snip]
>
> I have no problem with the directory structure - it is how inherited properties
> get moved/copied that is the big messy question.
>
> 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.

Since it's a branch not a tag, it's open to changes. Go ahead and
remove any iprops you dislike after copying?

> 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)

All iprops, as well as all regular properties that reside directly on
an object should be copied all of the time. Parent's iprops should
never be copied. Anything else would be inconsistent and impossible
to explain to users.

If you have a need to branch-then-remove-iprop as above, you've
probably applied the iprop to a wrong item in the first place? Move
it up a few layers in your tree. If you find that another tag wrongly
applies to tags or branches you create, it should probably be moved a
few notches down the tree.

It might be a bit worrying that all your existing tags can be affected
by changing iprops on their *parent* folders, however..

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 21 18:21:16 2005

This is an archived mail posted to the Subversion Dev mailing list.