All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Moreira-Guedes <codeagain@codeagain.dev>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	outreachy@lists.linux.dev,
	Bruno's Patch Watchbox <patch-reply@codeagain.dev>
Subject: Re: [PATCH 2/2] Docs: Update kernel series in changes.rst
Date: Tue, 19 Apr 2022 09:53:10 -0300	[thread overview]
Message-ID: <20220419125310.fss5634pxzujwkfg@AN5Bruno> (raw)
In-Reply-To: <Yl4nOBlKnWIcGcYS@casper.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

On Tue, Apr 19, 2022 at 04:06:32AM +0100, Matthew Wilcox wrote:
> On Mon, Apr 18, 2022 at 11:58:35PM -0300, Bruno Moreira-Guedes wrote:
> >  This document is designed to provide a list of the minimum levels of
> > -software necessary to run the 4.x kernels.
> > +software necessary to run the 5.x kernels.
> 
> We don't change the major version when we update the minimum required
> tooling ... why not change this once and for all to say:
> 
> +software necessary to build the current kernel.

Indeed it makes much more sense, I'm making a v2 soon!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2022-04-19 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19  2:57 [PATCH 0/2] Docs: Update information at changes.rst Bruno Moreira-Guedes
2022-04-19  2:57 ` [PATCH 1/2] Docs: Add cpio requirement to changes.rst Bruno Moreira-Guedes
2022-04-19  2:58 ` [PATCH 2/2] Docs: Update kernel series in changes.rst Bruno Moreira-Guedes
2022-04-19  3:06   ` Matthew Wilcox
2022-04-19 12:53     ` Bruno Moreira-Guedes [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=20220419125310.fss5634pxzujwkfg@AN5Bruno \
    --to=codeagain@codeagain.dev \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=outreachy@lists.linux.dev \
    --cc=patch-reply@codeagain.dev \
    --cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.