Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches | netdev | Ratatoskr

[PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Jakub Kicinski <kuba@kernel.org> · 2023-03-27
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Jacob Keller <jacob.e.keller@intel.com> · 2023-03-27
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Florian Fainelli <f.fainelli@gmail.com> · 2023-03-27
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Jakub Kicinski <kuba@kernel.org> · 2023-03-29
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · patchwork-bot+netdevbpf@kernel.org · 2023-03-29
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Thorsten Leemhuis <hidden> · 2023-03-29
Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches · Jakub Kicinski <kuba@kernel.org> · 2023-03-29

Re: [PATCH net-next] docs: netdev: clarify the need to sending reverts as patches

From: Jakub Kicinski <kuba@kernel.org>
Date: 2023-03-29 02:04:47
Also in: linux-doc

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!