Re: RFC: Log Message Templates via new hook.

Hi,

If I may try to close the 'GUI' part of this thread:

I think I found a way for TSVN to get around the network turnaround and
still leave the user/admin the choice to get it back:

- I will add a new value to the tsvn:logtemplate 'project property'
(TSVN's invention of server dictated configurations), 'repository'. If
that property has the value 'dynamic' or 'static' (which in no way could
be misinterpreted as a real log message template), then TSVN will
contact the repository to ask for the template.
- if the value is 'static', then the template is asked without the file
list to commit
- if the value is 'dynamic', the template is asked after the file list
is known (and the user prevented from entering the log message
beforehand), with some information shown so the user knows he has to
wait for the template to arrive.

That way, Subversion can implement the log message template as proposed
with the hook script on the server.

The only thing I request from you guys is that once inherited properties
are implemented, you define a property which does the same thing as the
TSVN project property I will use until then.

I hope we can all live with such an implementation?

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org