Re: RFC: Log Message Templates via new hook.

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).
>
> b) All projects under a common folder and all branches under a different
> common folder - if you only had two templates, you would again apply
> them to the highest directory which contains all of the folders which
> that template should apply to.
>
> c) Some mixed style repository - you are always free to create the log
> template iprop immediately after the copy (in fact you could probably do
> this in a post-commit hook).

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

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org