Re: RFC: Log Message Templates via new hook.

Ok, having stuck my nose into this early on and saying that I liked
the "server template hook" idea, I think that I have come around to
a different view.

The annoying thing is that I still like the concept of the server-side
hook but in actual use, I can not see it as a major benefit.

The directory properties (more specifically iprops) sounds like a
winner, but I have some concerns:

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

2) This now would depend on server->client config or iprops.
That is fine by me since I really want server-controlled auto-props
but simple template work is a "good thing" as many have used
it with CVS and to good effect.

3) If we don't do ipops, do we just say that the template is not
there for you if you checked out just a sub part of the tree which
does not have a template property? Maybe that is the correct
answer until we can figure out the "maze of trwisty iprop" issues
out. (Or does that add yet another twisty mess?)

> John Peacock <jpeacock@rowman.com> writes:
>
> > Here's a couple of ideas for dealing with conflicts (straight from my
> > brain to your eyes, no thought to complexity of implementation):
> >
> > 1) Highest One Wins - the template in force for the shortest path that
> > contains all committed file paths.

Well, other than strange command line commit operations where the
parent does not exist locally (which is possible??) this is the correct
behavior IMHO.

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