Re: RFC: Log Message Templates via new hook.

steveking wrote:
> But I can already see users
> complaining: they just wrote a very thorough log message which took them
> some time to write. Now they can just throw it away? Or re-edit it
> (which is basically the same)?

If the site admin has chosen to implement log-templates, we have to
assume it is for a very good reason, and the user will have to either
use those templates or override them (either GUI or CLI). And this is
something that the user has to get used to when working on that project.
  Besides, I hope the performance isn't _so_ bad that the user has that
much time to write a really long message. ;-)

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

Obviously I'm in favor of this... :-)

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

I'm not opposed to this, but I'm also not sure that it's necessary
either. We shouldn't get too caught up in the possibly obscure edge
case to see that we can get 90+% of the cases simply and without making
the last 10% completely impossible.

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