You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/09/15 10:17:21 UTC
[jira] [Resolved] (INFRA-12553) Mixed up tapestry-dev and
tapestry-commits archives
[ https://issues.apache.org/jira/browse/INFRA-12553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb resolved INFRA-12553.
--------------------------
Resolution: Fixed
> Mixed up tapestry-dev and tapestry-commits archives
> ---------------------------------------------------
>
> Key: INFRA-12553
> URL: https://issues.apache.org/jira/browse/INFRA-12553
> Project: Infrastructure
> Issue Type: Bug
> Components: Mail Archives
> Reporter: Sebb
> Assignee: Chris Lambertus
> Priority: Minor
>
> There's something very odd about the archives for tapestry-dev and tapestry-commits.
> If you compare the headers of
> http://mail-archives.apache.org/mod_mbox/tapestry-dev/
> and
> http://mail-archives.apache.org/mod_mbox/tapestry-commits/
> they both appear to be for the same mailing list, i.e. commits@tapestry.apache.org
> However the number of emails for each month are different and tapestry-dev goes back to 2003, whereas tapestry-commits starts in 2006.
> It looks as though the tapestry-dev mailboxes may contain all the e-mails from tapestry-commits as well as the ones from tapestry-dev. I've not checked all the counts, but the ones I compared always show more in the dev list than the commit list.
> I don't know why the header information on the index page for tapestry-dev is wrong.
> But it looks as though the tapestry-dev archiver was accidentally subscribed to tapestry-commits when that mailing list was created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)