Re: RFC: Log Message Templates via new hook.

Michael Sweet wrote:
> 1. Per-directory templates

> 2. Basic substitution/expansion from a static template, e.g.:

> I'm not too concerned about *how* this functionality is provided,
> however it seems to me that #1 would be satisfied by a new
> svn:log-template directory property, #2 would be satisfied by a
> little API on the client side, and #3 would be satisfied by the
> existing pre-commit hook.

So the log template would be:

a) a versioned directory property (so the site admin could establish one
for each "project" or even per-directory);

b) cached in the client WC (does not require network access to retrieve);

c) automatically expanded using the normal keyword substitution rules
(along with the $Files$ keyword) prior to starting the $EDITOR.

I don't think #2 requires more than a very minimal alteration to the
client API to do this if we support inherited properties.

> I don't see how a dynamic template hook would be that useful since
> you can bypass the template by providing the log message directly
> in the commit...

Agreed. It seems like we can get almost all of the clever features of
the smart templates without requiring a very narrow API that does *only*
that with server-side hooks.

I hate to keep carping on this, but I think the real discussion for
server->client configuration should start with inherited properties
(files inherit from their containing directory; the server manages
directory inheritance on checkout). This more generic feature would
give us a way to support autoprops, directory-based log templates, and
other distributed property features.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org