From: Manuel <manuelebner@airmail.cc>
To: Jonathan Corbet <corbet@lwn.net>,
Collin Funk <collin.funk1@gmail.com>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux
Date: Sun, 08 Mar 2026 21:06:58 +0100 [thread overview]
Message-ID: <55df12ee41de28943298a1e2973d69573edc09f2.camel@airmail.cc> (raw)
In-Reply-To: <87ldg8af2j.fsf@trenco.lwn.net>
On Tue, 2026-03-03 at 12:27 -0700, Jonathan Corbet wrote:
>
> > > - Why my request to separate out the logically different changes were
> > > ignored.
> >
> > I split the patch into a series like i responded on Tue, 24 Feb 2026
> > 08:13:02
> > > > i will make a Patch series with the files split.
> >
> > Do you want me to send two patches, which are not in a patch series?
>
> No, I want you to separate the logical changes.
>
> - Sorting the entries in the list is one logical change.
>
> - Adding new items is a different one. If you mix it in with the sort,
> nobody can really see which items are new.
so I got that. I have a follow-up question.
should i make two or four patches?
[PATCH 1/2] ver_linux and changes.rst: addition and changes
[PATCH 2/2] ver_linux and changes.rst: sort
[PATCH 1/4] ver_linux: addition and changes
[PATCH 2/4] changes.rst: addition and changes
[PATCH 3/4] ver_linux: sort
[PATCH 4/4] changes.rst sort
Manuel
prev parent reply other threads:[~2026-03-08 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 18:24 Manuel Ebner
2026-03-02 18:26 ` [PATCH v3 1/2] workflow: process/changes.rst: sort and cleanup list Manuel Ebner
2026-03-03 16:58 ` [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux Jonathan Corbet
[not found] ` <8dec205e406364d14f7ddf3ea11695407a7980b4.camel@airmail.cc>
2026-03-03 19:27 ` Jonathan Corbet
2026-03-08 20:06 ` Manuel [this message]
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=55df12ee41de28943298a1e2973d69573edc09f2.camel@airmail.cc \
--to=manuelebner@airmail.cc \
--cc=collin.funk1@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/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