Re: RFC: Log Message Templates via new hook.

Mark Phippard wrote:
> 1) With many GUI tools, at least TortoiseSVN and Subclipse, the GUI does
> not know what files will be committed at the time it would have to request
> the message template.

>
> 2) TortoiseSVN lets the user start typing their commit message while the
> code is crawling the WC looking for the changes.

Both of these are basically the same thing: the two main GUI's are not able to
quickly create the actual full commit before the user gets bored. This is a
limitation of the GUI, since the CLI client has to do the same work, yet I am
not aware of anyone complaining that commits take too long to preprocess.

I don't think *any* solution should be primarily predicated on mediating the
poor performance of GUI's (which may specifically be due to poor O/S performance
outside of the scope of Subversion _or_ the GUI's). We should certainly take
into account anything we can do to improve the performance, but if either
server-hooks or inherited properties perform acceptably in the CLI, then that is
  suffient. If the GUI's have speed issues outside of the scope of Subversion,
that should not, IMNSHO, be a driving considering in any design discussion.

John

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