www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Querna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-3164) Hook: E-Mail notification
Date Thu, 16 Dec 2010 00:53:00 GMT

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

Paul Querna commented on INFRA-3164:
------------------------------------

It seems like "3. Email per commit", is the preferred method of commit notification -- people
bunch up big commits with Git-SVN today -- those are community issues more than infra issues.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message