The VXL Project

On 01/07/2013 04:36 AM, Ian Scott wrote:
> Regarding the new commit messages from the new repository...
> 
> Is there any way the new commit messages could include the deepest 
> common directory/file of the modified files in the subject line itself? 
> Or at least in a parsable header.
> 
> The old emails used to have this, and it allowed me to write email rules 
> about which commits I wanted to pay attention to. Now I have to click on 
> all the links in the emails to find out that they are in contrib 
> libraries I don't use.

This is all built in to the SF Allura infrastructure.  We didn't configure
anything for it.  The only option related to it I see is in the individual
user settings there is a "Subscriptions" tab under which one can enable or
disable notifications.

> I've tried looking into the svnnotify hook, as suggested on 
> https://sourceforge.net/apps/trac/sourceforge/wiki/Subversion%20hook%20scripts#svnnotify. 
> However Step 2:
> "Mouse over the Project Admin menu and select Feature Settings" doesn't 
> appear to work.

That is part of the SF Classic infrastructure we no longer use.

You'll have to ask SF folks in a support forum.

-Brad

I found another page about commit messages that appears relevant to 
Allura: 
https://sourceforge.net/p/forge/community-docs/Subversion/#adding-an-svnnotify-hook

I tried following its advice, and got as far as adding and customising 
the call to svnnotify to the the post-commit-user script. But it didn't 
work. No emails, no error reports.

The hook file I tried:

/usr/bin/svnnotify --repos-path "$1" --revision "$2" \
   --to "vxl-commit@..." \
   --subject-prefix "SF.net SVN: vxl-svn:" \
   --subject-cx --no-first-line --with-diff \
   -U "http://sourceforge.net/p/vxl/svn/%s" \
   --user-domain "users.sf.net" \
   --max-diff-length 100000 1>&2


Any suggestions?
Ian.

On 07/01/2013 14:41, Brad King wrote:
> On 01/07/2013 04:36 AM, Ian Scott wrote:
>> Regarding the new commit messages from the new repository...
>>
>> Is there any way the new commit messages could include the deepest
>> common directory/file of the modified files in the subject line itself?
>> Or at least in a parsable header.
>>
>> The old emails used to have this, and it allowed me to write email rules
>> about which commits I wanted to pay attention to. Now I have to click on
>> all the links in the emails to find out that they are in contrib
>> libraries I don't use.
>
> This is all built in to the SF Allura infrastructure.  We didn't configure
> anything for it.  The only option related to it I see is in the individual
> user settings there is a "Subscriptions" tab under which one can enable or
> disable notifications.
>
>> I've tried looking into the svnnotify hook, as suggested on
>> https://sourceforge.net/apps/trac/sourceforge/wiki/Subversion%20hook%20scripts#svnnotify.
>> However Step 2:
>> "Mouse over the Project Admin menu and select Feature Settings" doesn't
>> appear to work.
>
> That is part of the SF Classic infrastructure we no longer use.
>
> You'll have to ask SF folks in a support forum.
>
> -Brad
>

On 01/07/2013 11:38 AM, Ian Scott wrote:
> I found another page about commit messages that appears relevant to 
> Allura: 
> https://sourceforge.net/p/forge/community-docs/Subversion/#adding-an-svnnotify-hook
> 
> I tried following its advice, and got as far as adding and customising 
> the call to svnnotify to the the post-commit-user script. But it didn't 
> work. No emails, no error reports.
> 
> The hook file I tried:
> 
> /usr/bin/svnnotify --repos-path "$1" --revision "$2" \
>    --to "vxl-commit@..." \
>    --subject-prefix "SF.net SVN: vxl-svn:" \
>    --subject-cx --no-first-line --with-diff \
>    -U "http://sourceforge.net/p/vxl/svn/%s" \
>    --user-domain "users.sf.net" \
>    --max-diff-length 100000 1>&2
> 
> 
> Any suggestions?

Did you set post-commit-user to be executable?

-Brad

On 01/07/2013 11:59 AM, Brad King wrote:
> On 01/07/2013 11:38 AM, Ian Scott wrote:
>> The hook file I tried:
>>
>> /usr/bin/svnnotify --repos-path "$1" --revision "$2" \
> 
> Did you set post-commit-user to be executable?

While at it, can you please look at restoring the check-case-insensitive.py
and check-mime-type.pl hooks?  I think we had them in the old repo.

Thanks,
-Brad

OK, commit messages seem to work now.
Thanks, Ian!

 
--	Peter.




















--