gt;>> -- Forwarded message --
>>> From: Projects <aps...@apache.org>
>>> Date: 12 April 2018 at 03:00
>>> Subject: WARN: invalid asfext:pmc
>>> 'https://logging.apache.org/log4j/2.x/' in
>>> https://logging.apache
s.
>>
>>
>> -- Forwarded message ------
>> From: Projects <aps...@apache.org>
>> Date: 12 April 2018 at 03:00
>> Subject: WARN: invalid asfext:pmc
>> 'https://logging.apache.org/log4j/2.x/' in
>> https://logging.apache.org/log4j/2.x/doap
2018 at 04:41, sebb <seb...@gmail.com> wrote:
> Please fix this.
>
>
> -- Forwarded message --
> From: Projects <aps...@apache.org>
> Date: 12 April 2018 at 03:00
> Subject: WARN: invalid asfext:pmc
> 'https://logging.apache.org/log4j/2.x/'
Please fix this.
-- Forwarded message --
From: Projects <aps...@apache.org>
Date: 12 April 2018 at 03:00
Subject: WARN: invalid asfext:pmc
'https://logging.apache.org/log4j/2.x/' in
https://logging.apache.org/log4j/2.x/doap_log4j.rdf
To: Site Development <site-...@a
> From: Projects <aps...@apache.org>
> Date: 10 April 2018 at 03:00
> Subject: WARN: invalid asfext:pmc
> 'https://logging.apache.org/log4j/2.x/' in
> https://logging.apache.org/log4j/2.x/doap_log4j.rdf
> To: Site Development <site-...@apache.org>
>
--
Matt Sicker <boa...@gmail.com>
As the subject says: the asfext:pmc value is incorrect; it must point
to a PMC not a release.
-- Forwarded message --
From: Projects <aps...@apache.org>
Date: 10 April 2018 at 03:00
Subject: WARN: invalid asfext:pmc
'https://logging.apache.org/log4j/2.x/' in
