From: Mike Snitzer <snitzer@redhat.com>
To: dm-devel@redhat.com
Subject: Re: dm-devel has migrated to lists.linux.dev
Date: Wed, 11 Oct 2023 14:41:58 -0400 [thread overview]
Message-ID: <ZSbsdlfRAoUj8Jzb@redhat.com> (raw)
In-Reply-To: <ZSCbqvX0f9LOXByf@redhat.com>
[this is also test, to see if new list allows old list to email it]
On Fri, Oct 06 2023 at 7:43P -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> On Fri, Oct 06 2023 at 7:29P -0400,
> Mike Snitzer <snitzer@kernel.org> wrote:
>
> > Hi,
> >
> > As a dm-devel@redhat.com subscriber, you have been silently subscribed
> > to the new mailing list: dm-devel@lists.linux.dev.
> >
> > Effective immediately, all dm-devel email should be addressed to:
> > dm-devel@lists.linux.dev
> >
> > (I say this but my "git pull" request that I just sent to Linus, to
> > update the MAINTAINERS file accordingly, cc'd dm-devel@redhat.com --
> > dm-devel@redhat.com will still function as it has, but nobody should
> > use it moving forward).
> >
> > If you do send email to dm-devel@redhat.com you will get this
> > auto-response:
> >
> > As of 2023.10.06: dm-devel@redhat.com has migrated to
> > dm-devel@lists.linux.dev
> >
> > If you were a dm-devel@redhat.com subscriber you have been silently
> > subscribed to dm-devel@lists.linux.dev
> >
> > NOTE: If you were a dm-devel@redhat.com subscriber but you disabled
> > mail delivery: then you must subscribe to dm-devel@lists.linux.dev.
> > To do so please send email to: dm-devel+subscribe@lists.linux.dev
> >
> > To unsubscribe from dm-devel@lists.linux.dev please send email to:
> > dm-devel+unsubscribe@lists.linux.dev
>
>
> Additional useful info:
>
> Please be sure to update any dm-devel mail filter you may have to look
> for this in mail headers:
> List-Id: <dm-devel.lists.linux.dev>
>
> Also, we will be backfilling "[dm-devel]" prefix for all list messages.
We cannot backfill the "[dm-devel]" prefix because that practice
breaks DKIM/DMARC.
Also, FYI: mail delivery has been disabled for all subscribers to
dm-devel@redhat.com, but the new list is subscribed and will relay any
mail sent to dm-devel@redhat.com to dm-devel@lists.linux.dev
(I've purposely sent this mail to dm-devel@redhat.com to test this
relay)
If/when you send mail to dm-devel@redhat.com you will still get an
autoresponse directing you to send future mail to
dm-devel@lists.linux.dev
Mike
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2023-10-11 18:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 23:29 dm-devel has migrated to lists.linux.dev Mike Snitzer
2023-10-06 23:43 ` Mike Snitzer
2023-10-11 14:35 ` Mike Snitzer
2023-10-11 18:28 ` Konstantin Ryabitsev
2023-10-11 18:41 ` Mike Snitzer [this message]
2023-10-11 18:52 ` Konstantin Ryabitsev
2023-10-11 20:08 ` Mike Snitzer
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=ZSbsdlfRAoUj8Jzb@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.