[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72k=WkiuKCQoOQFewbCcKATm7KZMV4jYBFmSSFryNKEAhQ@mail.gmail.com>
Date: Fri, 30 Jan 2026 21:11:52 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Tamir Duberstein <tamird@...nel.org>
Cc: Jesung Yang <y.j3ms.n@...il.com>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, Daniel Almeida <daniel.almeida@...labora.com>,
Fiona Behrens <me@...enk.dev>
Subject: Re: [PATCH 0/4] scripts: generate_rust_analyzer.py: tidy and add type hints
On Fri, Jan 30, 2026 at 8:57 PM Tamir Duberstein <tamird@...nel.org> wrote:
>
> Applied to rust-analyzer-next, thanks all!
To clarify, in most cases, branches are supposed to start from a tag
from Linus, not something in between his tags.
In addition, the idea was that you would start applying patches next
cycle, i.e. normally the branch should start applying patches with an
-rc1 or -rc2 base, rather than at this time of the cycle, and e.g.
finish around -rc5 time, and then you can send me your PR for that
cycle and so on.
Let's talk about it in the next meeting or we can schedule a call.
(The patches seem to be applied with the msgid link and with tags
collected, so that is fine :)
Cheers,
Miguel
Powered by blists - more mailing lists