From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: dwarves@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-rt-users@vger.kernel.org, linux-rtc@vger.kernel.org,
linux-trace-devel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
live-patching@vger.kernel.org
Subject: This list is being migrated to new infrastructure
Date: Wed, 20 Sep 2023 15:52:05 -0400 [thread overview]
Message-ID: <20230920-uncouple-grime-729f33@meerkat> (raw)
Hello, all:
This list is being migrated to the new vger infrastructure. This should be a
fully transparent process and you don't need to change anything about how you
participate with the list or how you receive mail.
There will be a brief 20-minute delay with archives on lore.kernel.org. I will
follow up once the archive migration has been completed.
Best regards,
Konstantin
next reply other threads:[~2023-09-20 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 19:52 Konstantin Ryabitsev [this message]
2023-09-20 20:15 ` This list is being migrated to new infrastructure 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=20230920-uncouple-grime-729f33@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=dwarves@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=live-patching@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 read-only IMAP folder(s) and NNTP newsgroup(s).