Re: RFC: Log Message Templates via new hook.

steveking wrote:
> But there's another way to go here:
> - have a log message template stored somewhere in the working copy
> (inherited property, normal property, ...) which a client can use.

> - that property can either be a complete log message template, or have a
> special value which indicates that the repository has to be contacted.
> - That special value also indicates if the change-files-list has to be
> sent to the server or not

That's a crazy amount of work for something that will never be used in reality.

It's a good thing to design for the future though.

For now, a static template (with a $Files$ keyword and a pre-commit
hook that replaces the keyword or rejects the commit) will do fine.

In the future, when people start creeping out of the twilight zone
with requests for templates which require a network turn-around, your
suggested way of doing things can be elegantly applied on top:
If a (i-)property named 'svn:server-template' exists on any of the
items to be committed, a future client should go directly to the
server and fetch a dynamic template.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 21 18:31:37 2005