Re: [PATCH] hook script for log message newline enforcement

kfogel@collab.net wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
>
>>>THE HOOK ALTERNATIVE:
>>+1
>>
>>>THE PROPOSAL:
>>-1

As I undestand, this mean next. If someone want reformat log messages on
server side, he must use hook for it.

But what about client software? On input only client software know
exactly does or does not user want put blank line at the end of log
message. EOL (end of line) before EOF (end of file) is de facto standard
for text files and all text editor do it (except for hex editors). This
is not mean blank line at the end and "svn ci -F" and "svn ci" must know
that. On output only client software know exactly is newline at the end
needed. For instance "svn log" must always put it, while some GUI client
should not.

Hook don't solve all problems. But if you do it, can you also make hook
to remove all trailing whitespaces, please. :) Because this is
compatible with current behavior of "svn log".

-- 
Olleg Samoylov