From: Jakub Kicinski <kuba@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches
Date: Tue, 28 Mar 2023 19:04:40 -0700 [thread overview]
Message-ID: <20230328190440.0f918125@kernel.org> (raw)
In-Reply-To: <7975a642-965b-81c7-d0e7-21e499b152ea@gmail.com>
On Mon, 27 Mar 2023 12:19:14 -0700 Florian Fainelli wrote:
> I would write immutable instead of stable here to convey the idea that
> there are no history rewrites once the tree is pushed out.
I'll s/stable/immutable/ when applying, thanks!
next prev parent reply other threads:[~2023-03-29 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 17:26 [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches Jakub Kicinski
2023-03-27 17:52 ` Jacob Keller
2023-03-27 19:19 ` Florian Fainelli
2023-03-29 2:04 ` Jakub Kicinski [this message]
2023-03-29 7:00 ` patchwork-bot+netdevbpf
2023-03-29 9:04 ` Thorsten Leemhuis
2023-03-29 19:02 ` Jakub Kicinski
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=20230328190440.0f918125@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).