From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@lists.linux.dev
Subject: lvm-devel has migrated to lists.linux.dev [was: Re: Welcome to the "lvm-devel" mailing list]
Date: Fri, 20 Oct 2023 17:34:36 -0400 [thread overview]
Message-ID: <ZTLybIL0gBcfDEe2@redhat.com> (raw)
In-Reply-To: <mailman.0.1697833396.3533474.lvm-devel@redhat.com>
Hi,
[Sorry for the noise of the previous mailman email, please ignore it.]
As a lvm-devel@redhat.com subscriber, you have been silently subscribed
to the new mailing list: lvm-devel@lists.linux.dev.
Effective immediately, all lvm-devel email should be addressed to:
lvm-devel@lists.linux.dev
If you do send email to lvm-devel@redhat.com you will get this
auto-response:
Your email to lvm-devel@redhat.com was delivered using
lvm-devel@lists.linux.dev because:
As of 2023.10.20: lvm-devel@redhat.com has migrated to
lvm-devel@lists.linux.dev
Please update the lvm-devel address to lvm-devel@lists.linux.dev
If you were a lvm-devel@redhat.com subscriber you have been silently
subscribed to lvm-devel@lists.linux.dev
Please be sure to update any lvm-devel mail filter you may have to look
for this in mail headers:
List-Id: <lvm-devel.lists.linux.dev>
NOTE: If you, or a friend, were a lvm-devel@redhat.com subscriber
with disabled mail delivery: then you must subscribe to
lvm-devel@lists.linux.dev. To do so please send email to:
lvm-devel+subscribe@lists.linux.dev
To unsubscribe from lvm-devel@lists.linux.dev please send email to:
lvm-devel+unsubscribe@lists.linux.dev
The lvm-devel list archive will soon be migrating here:
https://lore.kernel.org/lvm-devel/
Please let me know if you have any questions or concerns.
Thanks,
Mike
next parent reply other threads:[~2023-10-20 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1697833396.3533474.lvm-devel@redhat.com>
2023-10-20 21:34 ` Mike Snitzer [this message]
2023-10-23 14:43 ` lvm-devel has migrated to lists.linux.dev [was: Re: Welcome to the "lvm-devel" mailing list] 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=ZTLybIL0gBcfDEe2@redhat.com \
--to=snitzer@redhat.com \
--cc=lvm-devel@lists.linux.dev \
/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