[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c888efc-4b02-3470-8659-9922774f4fa7@gmail.com>
Date: Sun, 16 Oct 2022 08:50:14 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Olliver Schinagl <oliver+list@...inagl.nl>,
Gary Guo <gary@...yguo.net>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Miguel Ojeda <ojeda@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
rust-for-linux <rust-for-linux@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/13] [RFC] Rust support
On 10/16/22 08:44, Bagas Sanjaya wrote:
>
> I have to say two advices:
>
> First, don't top-post. I don't know what context you're replying to
> (in fact I have to cut the reply context below your message).
>
> Second, please post the patch inline, not attached. git format-patch +
> git send-email should suffice.
>
Oh, I forget to mention this. Is it RFC? If so, you need to specify
--subject-prefix="RFC PATCH" to git format-patch.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists