From: Oliver Mangold <oliver.mangold@pm.me>
To: Andreas Hindborg <a.hindborg@kernel.org>
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v2] rust: adding UniqueRefCounted and UniqueRef types
Date: Fri, 28 Feb 2025 19:47:16 +0000 [thread overview]
Message-ID: <Z8ISv6QfyLnU78K_@laptop> (raw)
In-Reply-To: <87mse5lvlq.fsf@kernel.org>
On 250228 2025, Andreas Hindborg wrote:
>
> I am using protonmail-bridge for sending as well. I don't think the
> issue is in the bridge, it must be in the way you compose/reply in mutt.
> I am not a mutt user, so I don't know how that works.
>
I'm usually just doing group-reply. What I read is that protonmail-bridge
drops 'in-reply-to' if there is no 'references', which looks about right,
when I check last mails. Need to find out, why the 'references' vanishes
sometimes, though.
Oliver
next prev parent reply other threads:[~2025-02-28 19:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 18:22 [PATCH v2] rust: adding UniqueRefCounted and UniqueRef types Oliver Mangold
2025-02-28 18:33 ` Boqun Feng
2025-02-28 19:01 ` Andreas Hindborg
2025-02-28 19:06 ` Boqun Feng
2025-02-28 19:16 ` Oliver Mangold
2025-02-28 19:25 ` Andreas Hindborg
2025-02-28 19:47 ` Oliver Mangold [this message]
2025-02-28 20:07 ` Oliver Mangold
-- strict thread matches above, loose matches on Subject: below --
2025-02-28 18:41 Oliver Mangold
2025-02-28 14:43 [PATCH] " Oliver Mangold
2025-02-28 18:01 ` [PATCH v2] " Oliver Mangold
2025-02-28 18:09 ` Boqun Feng
2025-02-28 18:16 ` Boqun Feng
2025-02-28 18:29 ` Andreas Hindborg
2025-03-03 14:09 ` Andreas Hindborg
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=Z8ISv6QfyLnU78K_@laptop \
--to=oliver.mangold@pm.me \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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.