[jira] [Commented] (INFRA-3164) Hook: E-Mail notification

["Jukka Zitting (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088684#comment-13088684 ] 

Jukka Zitting commented on INFRA-3164:
--------------------------------------

As discussed on infra@, since many projects manage multiple codebases (each of which would end up in a separate Git repository) but still have all the commit notifications sent to a single commits@ list. The main benefit of the path in the commit message subject is then to distinguish which codebase is being modified, which we should be able to do by including the Git repository name in the subject line. For example, a "gitified" Apache Commons project could see messages like these:

   commons-lang.git commit: Rewrite everything to Scala
   commons-math.git commit: Code for calculating the last digit of Pi
   commons-net.git commit: Implement RFC 3251


> Hook: E-Mail notification
> -------------------------
>
>                 Key: INFRA-3164
>                 URL: https://issues.apache.org/jira/browse/INFRA-3164
>             Project: Infrastructure
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Git
>            Reporter: Paul Querna
>            Priority: Trivial
>         Attachments: example-email.txt
>
>
> post-receive hook: E-Mail notification. We have a traditional
> dependence on 'good' commit emails. We need a very good mailer, as SvnMailer
> handles many cases like large commits, weird charactersets, etc, that most
> git based mailers don't even approach.
> I suggest using SvnMailer's Python code as a library, generating the diff using calls out to git, and then building the email from that diff (so, reusing all of SvnMailers magic for handling 
> Ideally, it would also have a similar (or the same) configuration file as SvnMailer.
> http://opensource.perlig.de/svnmailer/

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira