From: Jacob Keller <jacob.e.keller@intel•com>
To: Jakub Kicinski <kuba@kernel•org>,
Martin Habets <habetsm.xilinx@gmail•com>
Cc: <davem@davemloft•net>, <netdev@vger•kernel.org>,
<edumazet@google•com>, <pabeni@redhat•com>
Subject: Re: [PATCH net-next] docs: netdev: recommend against --in-reply-to
Date: Mon, 30 Oct 2023 14:10:52 -0700 [thread overview]
Message-ID: <342dee74-a131-400a-ba2b-32b45ab556e8@intel.com> (raw)
In-Reply-To: <20230824082930.3f42cf8b@kernel.org>
On 8/24/2023 8:29 AM, Jakub Kicinski wrote:
> On Thu, 24 Aug 2023 10:08:54 +0100 Martin Habets wrote:
>> On Wed, Aug 23, 2023 at 08:49:22AM -0700, Jakub Kicinski wrote:
>>> It's somewhat unfortunate but with (my?) the current tooling
>>> if people post new versions of a set in reply to an old version
>>> managing the review queue gets difficult. So recommend against it.
>>
>> Is this something NIPA could catch?
>
> I think so, but the whole thing makes me feel bad. I mean, if I was
> to sit down to write some code I should probably try to hack up
> my email client to allow force-breaking threads?
>
Yea if I were to do anything else here it would be figure out how to
make the tooling handle this better somehow rather than trying to
enforce not doing it.
However, I agree recommending avoiding this is good.
Thanks,
Jake
next prev parent reply other threads:[~2023-10-30 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 15:49 [PATCH net-next] docs: netdev: recommend against --in-reply-to Jakub Kicinski
2023-08-23 20:38 ` Przemek Kitszel
2023-08-24 9:08 ` Martin Habets
2023-08-24 15:29 ` Jakub Kicinski
2023-10-30 21:10 ` Jacob Keller [this message]
2023-08-24 18:30 ` patchwork-bot+netdevbpf
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=342dee74-a131-400a-ba2b-32b45ab556e8@intel.com \
--to=jacob.e.keller@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=habetsm.xilinx@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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