Re: $log$ keyword expansion with hook-scripts?

sorry for the late response, somehow i missed the nabble notification...

John Peacock-4 wrote:
>
> patrick wyss wrote:
>> hi,
>>
>> i wonder if anybody has implemented the $log$ keyword expansion as a
>> hook-script.
>> i think it should be fairly easy to implement it the way it worked in CVS
>
> It's not. There is no multiline keyword support in Subversion, so
> unless you want the $log$ to be one big line, you are out of luck.
>
>
but wouldn't it be possible to have some perl/python/whatsoever pre-commit
script which does add current comment after the first $log$.

or even better delete the whole log and fill in the output of "svn log"

would this realy be tricky to implement?

>> btw: yes, i read
>> http://subversion.tigris.org/faq.html#log-in-source
>> but i'm one of the "I don't care about that. I want to use it
>> anyway."-guys...
>
> Sorry. You may want to consider changing your process to include more
> useful comments in the source code or just have a post-commit script
> which updates a code-management tool like Trac (not that I particularly
> like Trac)...
>

the thing i like about having the log in the sources is that you quickly see
the files history without having to switch between tools. maybe someone's
working offfline (in an airplane...) etc.

another idea i had is that maybe we'll include some XML for gnerating the
project dokumentation into subversion. it would be perfect if you could
automatically have the revision history in the printed dokument...

patrick

-- 
View this message in context: http://www.nabble.com/%24log%24-in-Subversion--tp1512135p14803671.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org