From: Dirk Behme <dirk.behme@de.bosch.com>
To: "Daniel Almeida" <daniel.almeida@collabora.com>,
"Guilherme Giácomo Simões" <trintaeoitogc@gmail.com>
Cc: <rafael@kernel.org>, <ojeda@kernel.org>, <alex.gaynor@gmail.com>,
<boqun.feng@gmail.com>, <gary@garyguo.net>,
<bjorn3_gh@protonmail.com>, <benno.lossin@proton.me>,
<aliceryhl@google.com>, <mcgrof@kernel.org>,
<russ.weight@linux.dev>, <dakr@redhat.com>,
<a.hindborg@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] device: rust: change the name function
Date: Mon, 30 Sep 2024 06:33:33 +0200 [thread overview]
Message-ID: <51fe3ee3-0b81-418d-b05f-626dbcea4f57@de.bosch.com> (raw)
In-Reply-To: <32476CD7-74D6-4575-9D93-2FBCD5AE3E10@collabora.com>
On 29.09.2024 17:35, Daniel Almeida wrote:
> links may become stale,
> so please do not link to anything.
This sounds a little too general to me ;)
I mean we link a lot, using the 'Link' tag even in patches.
For example the mailing list archive has the 'permalink' button and
Zulip has the 'Copy link to message' button I think can be used.
> Lastly, I can’t see a diff anywhere.
Yes, I was confused by that, too. But I wonder if just the numbering is
wrong? I.e. if [PATCH 1/2] was intended to be the cover letter 0/1 and
the [PATCH 2/2] was intended to be the actual patch 1/1? Just a hint :)
Best regards
Dirk
next prev parent reply other threads:[~2024-09-30 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 13:30 Guilherme Giácomo Simões
2024-09-29 15:35 ` Daniel Almeida
2024-09-30 4:33 ` Dirk Behme [this message]
2024-09-30 11:14 ` Guilherme Giácomo Simões
2024-09-30 12:04 ` Miguel Ojeda
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=51fe3ee3-0b81-418d-b05f-626dbcea4f57@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--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=dakr@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=trintaeoitogc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®