On Sun, Sep 1, 2013 at 10:45 AM, Andrew Phillips <[email protected]> wrote:
>> Do you know if it would be possible to have emails from these  separate
>> place prefixed with [JIRA] or [GitHub] or [whatever] so  it's easy to filter
>> them client side?
>
>
> @mentors: do you have any info on this?
>
> I would suspect that the [...] prefixes (I think we already have [JIRA} and
> [commit] or something for the Jira and ASF Git emails?) are generated by the
> mail sender, not dependent on the mailing list. So hopefully they'd be
> preserved.
>
> As regards GitHub, BuildHive and DEV@cloud, I'm not sure what influence we
> have over the mail template - something to look into. The
> DEV@cloud/BuildHive emails are reasonably recognisable by the sender, but
> perhaps some mailing list processing rules could be set up..?
>
> ap

Git and Jira already have text in the subject that you could filter on.

Personally I am -0.5 on the idea of doing away with commits@. First,
it will never go away, all of that history in the list will have to be
preserved for posterity. Second, it's something of a design pattern at
the ASF - virtually every project has commits@ and it's almost an
expectation. There are also many places that assume a commits@ exist.

--David

Reply via email to