Re: RFC: Log Message Templates via new hook.

kfogel@collab.net wrote:

> Does this really solve anything?
>
> If the substitution does not happen while the log message is being
> written, then the user never sees the final version of their log
> message (and it's highly unlikely, I would think, that an unadorned
> list of files is what anyone wants in a log message, since that
> duplicates information already stored by the repository).
>
> In other words, if the user can't use the list of files at the time
> they're writing the log message (with or without template), then what
> good is the substitution variable?

You're right. That's why I suggested to not use a runtime param for the
hook script but a setting in the working copy (e.g. property, server
side configuration, inherited property, ...) which only states if the
hook script
- has to be called (if not, then the template is static and should also
be stored in the wc)
- has to be called with the complete file list (i.e. TSVN would have to
prevent the user from entering a log message until all files which get
committed are known)
- has to be called, but without a file list

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