Re: RFC: Log Message Templates via new hook.

Mark Phippard wrote:
> 2) TortoiseSVN lets the user start typing their commit message while the
> code is crawling the WC looking for the changes. Since the filenames have
> to be passed to the hook, they would have to drop this feature.

> I guess the other option is that the GUI's could call the hook up-front,
> and not pass it any files. By convention, hook authors would have to be
> aware of this and perhaps instructed to pass back a variable in the message
> template where files are to be inserted?

Sounds error-prone.

> Comments?

You're right.
GUI performance is going to suck if it's implemented as proposed (hook
script with filenames as parameters).

And that happens to be one of the absolute top subjects on the TSVN
list - GUI performance generally sucks in the Subversion GUI world.

*Some* of it could possibly be attributed to wrong implementation of
the GUI. But it seems that a lot of the performance issues with TSVN
stem from Subversion being developed without taking GUI performance
into consideration.

So it's a good point to raise.

(TSVN already has 2 different implementations of a status cache, and
talks about caching log messages are ongoing. I don't think they'd
love to have to maintain yet another cache for log templates.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 20 10:57:48 2005