From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Ariel Miculas <ariel.miculas@gmail.com>
Cc: Martin Rodriguez Reboredo <yakoyoku@gmail.com>,
Ariel Miculas <amiculas@cisco.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
benno.lossin@proton.me
Subject: Re: [PATCH v3] rust: helpers: sort includes alphabetically in rust/helpers.c
Date: Wed, 26 Apr 2023 23:28:16 +0200 [thread overview]
Message-ID: <CANiq72nX9uHanKZ4at80O3p-c2S8WM4SCRGF3f=PHdO3itEZUA@mail.gmail.com> (raw)
In-Reply-To: <CAPDJoNuX17h0=F7VRP=-VODG1bcdCYZAD+WNSofvpWPwwvbxMg@mail.gmail.com>
On Wed, Apr 26, 2023 at 11:04 PM Ariel Miculas <ariel.miculas@gmail.com> wrote:
>
> This is the format I see in https://docs.kernel.org/process/5.Posting.html#
> ```
> Link: https://example.com/somewhere.html optional-other-stuff
> ```
> And looking briefly through the git log I see the simple `Link:
> www.example.com` format.
Indeed, the one you have in the commit is the right one :)
There are 5 commits in the kernel with the format mentioned by Martin,
but they were probably unintentional.
Cheers,
Miguel
next prev parent reply other threads:[~2023-04-26 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 20:28 [PATCH] rust: Sort rust/helpers.c's #include directives Ariel Miculas
2023-04-25 20:37 ` Miguel Ojeda
2023-04-26 8:13 ` Ariel Miculas
2023-04-26 8:23 ` Ariel Miculas
2023-04-26 8:17 ` Ariel Miculas
2023-04-26 17:55 ` Miguel Ojeda
2023-04-26 20:49 ` [PATCH v3] rust: helpers: sort includes alphabetically in rust/helpers.c Ariel Miculas
2023-04-26 20:55 ` Martin Rodriguez Reboredo
2023-04-26 21:04 ` Ariel Miculas
2023-04-26 21:28 ` Miguel Ojeda [this message]
2023-04-27 12:36 ` Gary Guo
2023-07-19 20:01 ` 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='CANiq72nX9uHanKZ4at80O3p-c2S8WM4SCRGF3f=PHdO3itEZUA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=amiculas@cisco.com \
--cc=ariel.miculas@gmail.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=wedsonaf@gmail.com \
--cc=yakoyoku@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;
as well as URLs for NNTP newsgroup(s).