From: stephano <stephano.cetola@linux.intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Mailing List Move Day Set: April 4th
Date: Mon, 25 Mar 2019 09:21:25 -0700 [thread overview]
Message-ID: <520cc50a-bb52-d24e-4c73-eb8cd8b0a312@linux.intel.com> (raw)
In-Reply-To: <bd0f757d-1b8d-0602-101b-1242eed53135@redhat.com>
On 3/25/2019 5:51 AM, Laszlo Ersek wrote:
> Hi Stephano,
>
> Can you please confirm that the current mailing list archive URLs will
> continue working?
Yes, I'll check on this today.
> Personally, when I provide archive links (in discussions, BZs, commit
> messages etc), I tend to make sure that I include two links: one into
> the master archive, and another (to the same message) into the
> mail-archive.com archive. From these, I make sure that the 2nd one is
> always a Message-ID-based URL. The benefit is that, even if
> mail-archive.com disappears, people can construct new URLs to old
> messages, from the old message-IDs that are captured in the old URLs --
> assuming a new archive service exposes the old messages by message-ID again.
This is a good point and shows the level of detail that is preserved by
the mailing list if maintained properly. I would assume this is part of
the reason that the Linux kernel has continued to use mailing lists for
patch review as this level of detail is highly desired in their case.
> In brief, please preseve the archive at
> <https://lists.01.org/pipermail/edk2-devel/>, albeit with locked down
> content, indefinitely.
Will do.
Cheers,
Stephano
next prev parent reply other threads:[~2019-03-25 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 0:41 [edk2-announce] Mailing List Move Day Set: April 4th stephano
2019-03-25 12:51 ` Laszlo Ersek
2019-03-25 16:21 ` stephano [this message]
2019-03-25 22:21 ` Rebecca Cran
2019-03-26 12:07 ` Laszlo Ersek
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=520cc50a-bb52-d24e-4c73-eb8cd8b0a312@linux.intel.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