svn commit: [svnbook source]: www/index.en.html
C. Michael Pilato
cmpilato at gmail.com
Thu Aug 6 16:00:51 CDT 2015
Well, that worked. But I changed it again to match the format we used for
years on Google code:
[svnbook] r1234 committed - Blah blah blah
On Thu, Aug 6, 2015 at 4:50 PM, C. Michael Pilato <cmpilato at gmail.com>
> On Tue, May 5, 2015 at 6:11 PM, Daniel Shahaf <d.s at daniel.shahaf.name>
>> C. Michael Pilato wrote on Mon, May 04, 2015 at 10:29:43 -0400:
>> > I think this means the new svnnotify hook script is working. Yay!
>> May I suggest changing "5038" to "r5038" in the subject? That would
>> make mailbox grepping (copy-paste revnums into MUA's search box) easier.
>> I don't believe I have access to the svnnotify script, but it might be
>> just a matter of changing
>> --revision "$2"
>> --revision "r$2"
>> if the script treats that parameter as a string.
> Finally getting around to dealing with this. Sorry. #life
> There's not much to go on by way of information, but I believe that
> SourceForge's svnnotify is a modified version of the script found here:
> That one appears to really just want a revision number (integer) for the
> --revision parameter. But there does appear to be a way to tweak the
> Subject line to achieve the formatting you desire:
> svnnotify --subject-prefix [Devlist]
> svnnotify -P [%d (Our-Developers)]
> An optional string to prepend to the beginning of the subject line of the
> notification email. If it contains '%d', it will be used to place the
> number; otherwise it will simply be prepended to the subject, which will
> contain the revision number in brackets.
> So, I'll give the following a shot:
> --subject-prefix "svn commit: [svnbook source]:[r%d]"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the svnbook-dev