Re: r11945: Explanation of %MESSAGEFILE% parameter for start-commit hook.

On Jan 29, 2008 2:06 AM, Lübbe Onken | RA Consulting <l.onken_at_rac.de> wrote:
> Hi Alexander (or someone else)
>
> Could you please rephrase the sentence:
> "After successful execution of start-commit hook log message is read back, giving the hook a chance to modify it."
> in dug-settings-hooks.xml?
>
> I have trouble understanding what the author intended to say. Maybe just insert an article at the proper place ;)

Sorry, I thought the docs in bad English are better then no docs at all ;-)

I hope the explanation below will help to rephrase it better:
1) TortoiseProc writes commit message to %MESSAGEFILE%
2) TortoiseProc calls start-commit hook
3) Hook reads and/or writes %MESSAGEFILE%
4) Hook returns exit value
5) If said value is zero, indicating success,
  TortoiseProc reads %MESSAGEFILE% and uses its content
  as a new commit message

See also recent mail thread about "Log message sources priority".

-- 
Alexander S. Klenin
Insight Experts Ltd.