All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 0/2] Two small cleanups to maintainers_include
Date: Mon, 25 May 2026 14:28:15 -0600	[thread overview]
Message-ID: <87qzmzz128.fsf@trenco.lwn.net> (raw)
In-Reply-To: <cover.1778952682.git.mchehab+huawei@kernel.org>

Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:

> Hi Jon,
>
> This series contain two minor cleanups to maintainers_include.py:
>
> - make it backward compatible with Python < 3.10
>   (according with vermin, it should now be backward-compat up
>    to 3.6)
>
> - keep "THE REST" at the end.
>
> Mauro Carvalho Chehab (2):
>   docs: maintainers_include: restore compatibility with Python 3.6
>   docs: maintainers_include: keep the last entry at the end
>
>  Documentation/sphinx/maintainers_include.py | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2026-05-25 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-16 17:33 [PATCH 0/2] Two small cleanups to maintainers_include Mauro Carvalho Chehab
2026-05-16 17:33 ` [PATCH 1/2] docs: maintainers_include: restore compatibility with Python 3.6 Mauro Carvalho Chehab
2026-05-16 17:33 ` [PATCH 2/2] docs: maintainers_include: keep the last entry at the end Mauro Carvalho Chehab
2026-05-25 20:28 ` Jonathan Corbet [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=87qzmzz128.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=skhan@linuxfoundation.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.