www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-3771) CMS commit email flooding
Date Wed, 13 Jul 2011 21:50:59 GMT

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

#asfinfra IRC Bot commented on INFRA-3771:
------------------------------------------

<danielsh> the fix was r792669


> CMS commit email flooding
> -------------------------
>
>                 Key: INFRA-3771
>                 URL: https://issues.apache.org/jira/browse/INFRA-3771
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: CMS, Subversion
>            Reporter: David Blevins
>            Assignee: David Blevins
>            Priority: Minor
>
> Not sure how things are setup, but would excellent if we could lower the threshold on
when commit messages from ' /websites/staging/' get sent as one email because it exceeds the
cap.
> Typically I see:
> [This commit notification would consist of 71 parts,
> which exceeds the limit of 50 ones, so it was shortened to the summary.]
> We're getting bit as we're right at 49 with '/websites/staging/openejb'.  Maybe a limit
of 40 instead?
> I don't think anyone would realistically review even 40 pages of generated html, but
that's another issue I suppose.

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

        

Mime
View raw message