Re: RFC: Log Message Templates via new hook.

Greg Hudson wrote:
> ...
>>If these are the underlying assumptions, then why won't the
>>per-directory static template work?
>
>
> I commit twenty files in ten widely separated directories. Which
> directory's template gets used?
>
> This is one of the questions Karl initially started out trying to
> answer, and he found that the answer wasn't obvious, which led him to
> the idea of punting to a server hook. Yet you and four other of this
> morning's contributors to the conversation seem to have simply glossed
> over the question, instead considering issues like how the user might
> easily set the same template for many directories. Perhaps you all have
> some simple, adequate idea in mind ("the template for the anchor of the
> commit", perhaps), but I really can't tell.

Well, I for one missed this issue in all of the discussions... :)

I, for one, would never use a different template for the same
project, however it is conceivable that I might commit from a
top-level directory to apply changes to multiple projects in one
go, say to update a copyright or license file that is common.

In that case, I think I would want the top-level directory's
log template to take precedence. The alternative is to ask for
several log messages, which means the commit would no longer be
atomic.

So, for the proposed svn:log-template iprop, the client would use
iprop for the directory you are committing from. If you specify
the directories by hand, e.g.:

     svn ci foo/bar1 foo/bar2 foo/bar3/bla

then the common root directory ("foo" in this case) would be used
to grab the svn:log-template iprop.

If a project does not want to allow multi-project commits, then
they can use the pre-commit hook to reject them (right? :)

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
Internet Printing and Document Software          http://www.easysw.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org