From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: Test delivery and archive propagation
Date: Tue, 18 Jul 2023 21:56:23 +0200 [thread overview]
Message-ID: <CANiq72mdQmV0MJUhGCtj1MON4+Tb2bbKSkyjmM_ayeEBgc1HgA@mail.gmail.com> (raw)
In-Reply-To: <20230718-refinance-levitator-cf0be1@meerkat>
On Tue, Jul 18, 2023 at 8:05 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> This list has been migrated to its new location on the LF "subspace" system.
> There is no action required on your part -- it should be a fully transparent
> migration.
>
> This message serves as a propagation test to make sure that the archives are
> properly replicating.
Thanks Konstantin (& John)!
Trevor asked in Zulip if this fixes the patch limit: yes, it should,
from what I understand, so the need to Cc patches@lists.linux.dev
becomes obsolete now, which is great.
Cheers,
Miguel
next prev parent reply other threads:[~2023-07-18 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 18:05 Test delivery and archive propagation Konstantin Ryabitsev
2023-07-18 19:56 ` Miguel Ojeda [this message]
2023-07-19 21:07 ` 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=CANiq72mdQmV0MJUhGCtj1MON4+Tb2bbKSkyjmM_ayeEBgc1HgA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=rust-for-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).