From: Laszlo Ersek <lersek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: efi kernel list <linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: the Mail Archive is now (again) subscribed to this list...
Date: Fri, 3 Mar 2017 10:50:10 +0100 [thread overview]
Message-ID: <f063d8b0-e6fc-b8db-00c2-8402acefd909@redhat.com> (raw)
... and so linux-efi finally has a public archive again (because GMANE
has been defunct for a while now):
https://www.mail-archive.com/linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/
Whoever administers this list, please consider updating the info box at:
http://vger.kernel.org/vger-lists.html#linux-efi
--*--
As a side note, regarding
http://vger.kernel.org/majordomo-info.html
"As of now, subscription support is not handled at the web!",
I would love to welcome Majordomo @ VGER.KERNEL.ORG to the 21st century,
if it only enabled web-based subscription (like practically all
pipermail / mailman2 instances do, while at the same time they do remain
sane, and resist the "web 2.0" idiocy).
I had to employ some "From:" hackery to subscribe the Mail Archive to
linux-efi <https://www.mail-archive.com/faq.html#newlist>, which,
combined with the extreme slowness of VGER.KERNEL.ORG, was decidedly
un-fun. (I'm lucky that the RH SMTP server didn't reject my "forged"
>From headers.)
Also, the info box at <http://vger.kernel.org/vger-lists.html#linux-efi>
is almost entirely useless, it doesn't even tell me who runs linux-efi,
so that I could have contacted them in person, for adding the Mail
Archive directly to the subscriber list (a practice recommended by the
Mail Archive themselves, see the link above).
Examples:
https://lists.nongnu.org/mailman/listinfo/qemu-devel
"Qemu-devel list run by listhelper-moderate at nongnu.org"
https://lists.01.org/mailman/listinfo/edk2-devel
"edk2-devel list run by michael.d.kinney at intel.com, laurie.jarlstrom
at intel.com, jordan.l.justen at intel.com, webmaster at 01.org"
https://www.redhat.com/mailman/listinfo/vfio-users
"vfio-users list run by alwillia at redhat.com"
etc etc etc
next reply other threads:[~2017-03-03 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 9:50 Laszlo Ersek [this message]
[not found] ` <f063d8b0-e6fc-b8db-00c2-8402acefd909-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-04 8:02 ` the Mail Archive is now (again) subscribed to this list Lukas Wunner
[not found] ` <20170304080222.GA3042-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-03-04 9:24 ` Ard Biesheuvel
2017-04-14 8:50 ` linux-efi archive Lukas Wunner
[not found] ` <20170414085059.GA5508-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-04-17 21:49 ` Konstantin Ryabitsev
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-all 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=f063d8b0-e6fc-b8db-00c2-8402acefd909@redhat.com \
--to=lersek-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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