From: Paul Menzel <pmenzel@molgen.mpg.de>
To: NeilBrown <neilb@suse.de>
Cc: Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Zdenek Kabelac <zkabelac@redhat.com>,
linux-raid@vger.kernel.org, dm-devel@redhat.com
Subject: Problems with email threading (was: [dm-devel] [PATCH] md: fix a crash in mempool_free)
Date: Fri, 4 Nov 2022 06:52:20 +0100 [thread overview]
Message-ID: <adf2fc44-f3d4-d96b-09a6-8e916a6f8449@molgen.mpg.de> (raw)
In-Reply-To: <166753684502.19313.12105294223332649758@noble.neil.brown.name>
Dear Neil,
Just a heads-up, Mozilla Thunderbird 102.4.1 does not thread your message.
Your reply contains:
In-reply-to:
=?utf-8?q?=3Calpine=2ELRH=2E2=2E21=2E2211031121070=2E18305=40fi?=
=?utf-8?q?le01=2Eintranet=2Eprod=2Eint=2Erdu2=2Eredhat=2Ecom=3E?=
References:
=?utf-8?q?=3Calpine=2ELRH=2E2=2E21=2E2211031121070=2E18305=40fil?=
=?utf-8?q?e01=2Eintranet=2Eprod=2Eint=2Erdu2=2Eredhat=2Ecom=3E?=
Mikulas’ message has:
Message-ID:
<alpine.LRH.2.21.2211031121070.18305@file01.intranet.prod.int.rdu2.redhat.com>
It looks strange, that the message id, that does not seem to contain any
non-ASCII characters is „reencoded“. No idea, if it violates any
standards though.
Kind regards,
Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org, Song Liu <song@kernel.org>,
dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: [dm-devel] Problems with email threading (was: [PATCH] md: fix a crash in mempool_free)
Date: Fri, 4 Nov 2022 06:52:20 +0100 [thread overview]
Message-ID: <adf2fc44-f3d4-d96b-09a6-8e916a6f8449@molgen.mpg.de> (raw)
In-Reply-To: <166753684502.19313.12105294223332649758@noble.neil.brown.name>
Dear Neil,
Just a heads-up, Mozilla Thunderbird 102.4.1 does not thread your message.
Your reply contains:
In-reply-to:
=?utf-8?q?=3Calpine=2ELRH=2E2=2E21=2E2211031121070=2E18305=40fi?=
=?utf-8?q?le01=2Eintranet=2Eprod=2Eint=2Erdu2=2Eredhat=2Ecom=3E?=
References:
=?utf-8?q?=3Calpine=2ELRH=2E2=2E21=2E2211031121070=2E18305=40fil?=
=?utf-8?q?e01=2Eintranet=2Eprod=2Eint=2Erdu2=2Eredhat=2Ecom=3E?=
Mikulas’ message has:
Message-ID:
<alpine.LRH.2.21.2211031121070.18305@file01.intranet.prod.int.rdu2.redhat.com>
It looks strange, that the message id, that does not seem to contain any
non-ASCII characters is „reencoded“. No idea, if it violates any
standards though.
Kind regards,
Paul
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2022-11-04 5:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:23 [dm-devel] [PATCH] md: fix a crash in mempool_free Mikulas Patocka
2022-11-03 15:23 ` Mikulas Patocka
2022-11-04 4:40 ` [dm-devel] " NeilBrown
2022-11-04 4:40 ` NeilBrown
2022-11-04 5:52 ` Paul Menzel [this message]
2022-11-04 5:52 ` [dm-devel] Problems with email threading (was: [PATCH] md: fix a crash in mempool_free) Paul Menzel
2022-11-04 13:52 ` [dm-devel] [PATCH] md: fix a crash in mempool_free Mikulas Patocka
2022-11-04 13:52 ` Mikulas Patocka
2022-11-05 22:34 ` NeilBrown
2022-11-05 22:34 ` NeilBrown
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=adf2fc44-f3d4-d96b-09a6-8e916a6f8449@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=dm-devel@redhat.com \
--cc=guoqing.jiang@linux.dev \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=neilb@suse.de \
--cc=song@kernel.org \
--cc=zkabelac@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.