[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72kc8scJjSiSwj81OSdcYMrsj2AFUp+Dm6=p6PGfM0k+Lg@mail.gmail.com>
Date: Mon, 30 Sep 2024 14:04:16 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Dirk Behme <dirk.behme@...bosch.com>
Cc: Daniel Almeida <daniel.almeida@...labora.com>,
Guilherme Giácomo Simões <trintaeoitogc@...il.com>,
rafael@...nel.org, ojeda@...nel.org, alex.gaynor@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, aliceryhl@...gle.com, mcgrof@...nel.org,
russ.weight@...ux.dev, dakr@...hat.com, a.hindborg@...nel.org,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] device: rust: change the name function
On Mon, Sep 30, 2024 at 6:33 AM Dirk Behme <dirk.behme@...bosch.com> wrote:
>
> 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.
Yeah, it is fine using Links, as long as the commit message is
understandable, i.e. please keep the critical information in the
commit.
> 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 :)
Yeah, they also appear in two independent threads, and they shouldn't be.
Guilherme, please use `git format-patch` and `git send-email` (or `b4`
[1]), it will handle these details for you.
Thanks!
[1] https://b4.docs.kernel.org
Cheers,
Miguel
Powered by blists - more mailing lists