Re: RFC: Log Message Templates via new hook.

On 5/20/05, Branko Èibej <brane@xbc.nu> 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.]> >> In fact, "copy" and "branch" are *significantly* different. But they're> different in ways that don't have much bearing on the behaviour of> inherited properties.
Well, yes and no - copy and branch and tag and rename are all verydifferent operations by a semantic point of view even if they havesome mechanical similarities.
The problem is defining the difference with respect to things thatare not directly within the current tree but affect that tree.
For example, a tag would want to make the new tree just like thecurrent tree is - including any behaviors that are maybe not directlydefined in the tree but from its parent. (Not that one would normallycommit to a "tag" but that is a different story)
So, the question is how does this get handled without too much"user surprise" (the "least astonishment" principle)
If I knew the "perfect" (or even close) answer, I would not be asking :-)
-- Michael Sinz Technology and Engineering Director/Consultant"Starting Startups" mailto:Michael.Sinz_at_sinz.orgMy place on the web http://www.sinz.org/Michael.Sinz
Received on Sat May 21 01:12:38 2005