Re: RFC: Log Message Templates via new hook.

kfogel@collab.net wrote:
> As the user checks/unchecks different files and directories (perhaps
> the user is indecisive and keeps changing his mind about what will be
> in the commit), does TSVN re-crawl to discover whether the log message
> template needs to change based on the new target paths? If it does,
> how does the interface handle the time delay potentially involved in
> the re-crawl?
>
> I am not saying you haven't solved these problems. Maybe you have --
> but if so, then you have (IMHO) dealt with "huge complexity" :-).

If we can know in advance whether the repository _requires_ a with-files
template, then the commit dialog could become two stage.

1. User selects the files to use, and editing the log messages is
disabled.
2. Click a 'Next' button.
3. Get template from hook, shovel or friendly bacterium.
4. Fill in template and click 'Commit'.

But users who don't require the with-files template will hate having to
wait before typing the message. So we either need static/dynamic
recorded in a prop/iprop, or getting the without-files template has to
inform you that there is a with-files template which should override it.

Simon

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