[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250213174602.200524-1-trintaeoitogc@gmail.com>
Date: Thu, 13 Feb 2025 14:46:02 -0300
From: Guilherme Giacomo Simoes <trintaeoitogc@...il.com>
To: gary@...yguo.net
Cc: a.hindborg@...nel.org,
alex.gaynor@...il.com,
aliceryhl@...gle.com,
apw@...onical.com,
arnd@...db.de,
aswinunni01@...il.com,
axboe@...nel.dk,
benno.lossin@...ton.me,
bhelgaas@...gle.com,
bjorn3_gh@...tonmail.com,
boqun.feng@...il.com,
dakr@...nel.org,
dwaipayanray1@...il.com,
ethan.twardy@...il.com,
fujita.tomonori@...il.com,
gregkh@...uxfoundation.org,
joe@...ches.com,
linux-kernel@...r.kernel.org,
lukas.bulwahn@...il.com,
ojeda@...nel.org,
pbonzini@...hat.com,
rust-for-linux@...r.kernel.org,
tmgross@...ch.edu,
trintaeoitogc@...il.com,
walmeida@...rosoft.com
Subject: Re: [PATCH 2/3] rust: macros: change author field to array
Gary Guo <gary@...yguo.net> wrotes:
> Spelling out commit SHA doesn't work for patches because it will change
> when applied.
Hmm, I was think that they would stayed the same
> Also, this patch needs to be the same commit as the one changing
> macros, otherwise the tree won't compile when bisecting.
This really make sense, I will send a v2
Thanks,
Guilherme
Powered by blists - more mailing lists