[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 12:22:34 CEST

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


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 May 20 12:17:33 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.