[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nJSaR-_89Epe2gZc=5_N-xhUBV0W4rV0NAb2-OsQc51A@mail.gmail.com>
Date: Fri, 14 Oct 2022 18:12:11 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Geert Stappers <stappers@...ppers.nl>
Cc: Olof Johansson <olof@...om.net>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts: rust_is_available.sh: Provide hints on how to
fix missing pieces
Hi Geert,
On Thu, Oct 13, 2022 at 7:01 PM Geert Stappers <stappers@...ppers.nl> wrote:
>
> How to prevent that the patch gets lost in the mail?
Do not worry, it is not lost :)
> And how to avoid that reminders like this get contra-productive?
> (When to send the next "Please approve or reject the patch"?)
The author of the patch would normally send a ping. If you are
curious, please see Documentation/process/submitting-patches.rst for
some guidelines.
In short, the authors would wait at least a week, and they would apply
their best judgment (e.g. whether the merge window is going on,
whether it is a new feature or a critical fix, whether
feedback/comments/tags are still coming, etc.).
Cheers,
Miguel
Powered by blists - more mailing lists