From: Jonathan Corbet <corbet@lwn.net>
To: Manuel Ebner <manuelebner@airmail.cc>,
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,
Manuel Ebner <manuelebner@airmail.cc>
Subject: Re: [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux
Date: Tue, 03 Mar 2026 09:58:51 -0700 [thread overview]
Message-ID: <87wlzsdf3o.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260302182405.86829-2-manuelebner@airmail.cc>
Manuel Ebner <manuelebner@airmail.cc> writes:
> It is a pain in the ass to compare the software versions on the running
> system (scripts/ver_linux) with the minimal required versions (changes.rst).
> Sorting both lists the same way makes side-by-side comparisons a simple task.
>
> [v2] -> [v3]:
> fix changelog
> changes.rst:
> needn't -> do not need to
> add gdb 7.2
> ver_linux:
> /Changes.rst -> /changes.rst
> add gdb
Please explain to me:
- Why I am getting multiple copies of the same patches
- Why I'm getting the same series from a completely different identity;
the first set came from "Hans Anda"
- Why my request to separate out the logically different changes were
ignored.
Thanks,
jon
next prev parent reply other threads:[~2026-03-03 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 18:24 [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux 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 ` Jonathan Corbet [this message]
[not found] ` <8dec205e406364d14f7ddf3ea11695407a7980b4.camel@airmail.cc>
2026-03-03 19:27 ` [PATCH v3 0/2] workflow, scripts: sort changes.rst and ver_linux Jonathan Corbet
2026-03-08 20:06 ` Manuel
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=87wlzsdf3o.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=collin.funk1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuelebner@airmail.cc \
--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