From: "Laszlo Ersek" <lersek@redhat.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>
Cc: intelstephano <stephano.cetola@linux.intel.com>
Subject: Re: [edk2-announce] Welcome to the new mailing list!
Date: Mon, 8 Apr 2019 19:40:12 +0200 [thread overview]
Message-ID: <1a29b4ac-ecd3-de08-f4e0-5847849d4622@redhat.com> (raw)
In-Reply-To: <73a98dd2-11a3-b328-0051-f5d642661ab7@linux.intel.com>
(directing the answer to devel@)
Hi Stephano,
On 04/03/19 20:54, intelstephano wrote:
> The [edk2-bugs] mailing list will be transitioned to Groups.io once we
> have testing the devel mailing list and ensured success.
Unfortunately, the current <edk2-bugs@lists.01.org> mailing list seems
to have been disabled too early.
For example, while TianoCore#364 has <edk2-bugs@lists.01.org> on CC
(from the original default-CC), I've received no email notification of
your fresh comment#1 in that BZ:
https://bugzilla.tianocore.org/show_bug.cgi?id=364#c1
The latest message that I've personally received through
<edk2-bugs@lists.01.org> is exactly the latest message displayed in the
<edk2-bugs@lists.01.org> archive:
https://lists.01.org/pipermail/edk2-bugs/2019-April/006787.html
Can you please ask the lists.01.org admins to reenable
<edk2-bugs@lists.01.org> until:
- we set up the replacement list (and people get a chance to subscribe,
and configure their filters),
- and the <edk2-bugs@lists.01.org> CC address is replaced on all the
TianoCore BZ tickets, with the address of the new bugmail list?
Thanks!
Laszlo
next parent reply other threads:[~2019-04-08 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73a98dd2-11a3-b328-0051-f5d642661ab7@linux.intel.com>
2019-04-08 17:40 ` Laszlo Ersek [this message]
2019-04-09 0:31 ` [edk2-announce] Welcome to the new mailing list! Stephano Cetola
2019-04-09 8:11 ` Laszlo Ersek
2019-04-09 11:27 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-04-09 14:48 ` Stephano Cetola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a29b4ac-ecd3-de08-f4e0-5847849d4622@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox