Re: [PATCH] v2 Docs: changes.rst: introduce optional column

[Manuel Ebner <manuelebnerli@mailbox.org>]

On Fri, 2026-09-04 at 18:11 +0200, Nicolas Schier wrote:
> On Mon, Aug 31, 2026 at 05:25:22PM +0200, Manuel Ebner wrote:
> > The optional tag isn't obvious nor defined. Therefore replace with column.
> 
> Why do you throw away the 'Command to check the version' column?  

I would do this to get some space for the optional column and have
the version commands in ./scrips/ver_linux . See below.

> At 
> work, we have a script that uses these commands to check the actual 
> tooling versions.

Well, I don't want to break that.

> If there is a reason for change, please document it in the commit 
> message.

Will do.

> > Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> > ---
> >  Documentation/process/changes.rst | 84 +++++++++++++++----------------
> >  1 file changed, 42 insertions(+), 42 deletions(-)
> > 
> > diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> > index b3fa980b63e3..905ac0f6cdc5 100644
> > --- a/Documentation/process/changes.rst
> > +++ b/Documentation/process/changes.rst
> > @@ -29,49 +29,49 @@ systems; obviously, if you don't have any PC Card hardware, for example,
> >  you probably do not need to concern yourself with pcmciautils.
> >  
> >  ====================== ===============  ========================================
> > -        Program        Minimal version       Command to check the version
> > +        Program        Minimal version  Required for 
> 
> Do you want to align the column headers to the left or center them?

I should have done this the proper way but i didn't.

> >  ====================== ===============  ========================================
> > -bash                   4.2              bash --version
> > ...
> > +bash                   4.2              
> > ...
> >  ====================== ===============  ========================================
> >  
> >  .. [#f1] Sphinx is needed only to build the Kernel documentation
> 
> I kind of like the "Required for" column w/ naming 
> concrete Kconfig symbols or envs like ARCH.  

Thanks, do you prefer your scripts working or the required for column? Maybe there
is space for both, when 'program' and 'Minimal version' get squished.
Would one of those arrangements not break your scripts?

>  ====================== ===============  ================  =======================
>          Program        Minimal version    Required for        Version Command
>  ====================== ===============  ================  =======================

OR
>  ====================== ===============  =======================  ================
>          Program        Minimal version      Version Command        Required for
>  ====================== ===============  =======================  ================

> I think it would be good to 
> get this a bit more complete, where possible.

I have only little clue about tooling, versions or Kconfig so I'll need some help with that.

Thanks
 Manuel 

> Kind regards,
> Nicolas