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-3653) send Maven WAGON commit messages to maven-commits instead wagon-commits
Date Tue, 24 May 2011 21:32:47 GMT

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

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

<gmcdonald> gather all the changes you need to this issue so they cna be done in one
hit, thanks.


> send Maven WAGON commit messages to maven-commits instead wagon-commits
> -----------------------------------------------------------------------
>
>                 Key: INFRA-3653
>                 URL: https://issues.apache.org/jira/browse/INFRA-3653
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Subversion
>            Reporter: Mark Struberg
>
> Since traffic on a few maven subprojects is pretty low, we decided to consolidate our
mailing lists a bit.
> Currently committing to https://svn.apache.org/repos/asf/maven/wagon will send mails
to wagon-commits.
> There is almost zero traffic those days
> http://markmail.org/search/?q=list%3Aorg.apache.maven.wagon-commits
> thus moving this info over to maven-commits is what we'd like to have.
> The basic tendency is to aggregate those mailing litsts even more. Should I ping the
maven PMC and get a list which other projects should get folded too, or better create single
Jiras for each separate list?

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

Mime
View raw message