You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Paul Joseph Davis (JIRA)" <ji...@apache.org> on 2011/02/12 03:07:57 UTC

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

     [ https://issues.apache.org/jira/browse/INFRA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Joseph Davis updated INFRA-3164:
-------------------------------------

    Attachment: example-email.txt

Emails are now being generated as described. I'm attaching an example email so people can comment on parts they like or dislike. There are some parts of the edge cases that are a bit weird still mostly relating to cases when a ref update causes a large number of emails to be generated. I'll post a link to the docs that describe the current behaviour when I write them.

For now I'd like pointers on content and formatting or any other suggestions in that regard.

> 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