mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
		linux-doc@vger.kernel.org, Kees Cook <kees@kernel.org>
Subject: Re: [PATCH] MAINTAINERS: fix '*' wildcard formatting
Date: Thu, 05 Mar 2026 01:24:12 -0800	[thread overview]
Message-ID: <1d96c26a14026c7f914e95fba1af10e7a2726bda.camel@perches.com> (raw)
In-Reply-To: <20260304224201.1072044-1-rdunlap@infradead.org>

On Wed, 2026-03-04 at 14:42 -0800, Randy Dunlap wrote:
> It seems that these wildcards confuse some parser (docutils, sphinx,
> or maintainers_include.py), so quote them to avoid this issue.
> Also insert a hyphen ('-') before "all files" in several places
> to make the html output easier to read.
> 
> Fixes this htmldocs warning:
> 
> linux-next-20260304/MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]

I think there should be a better way than this.
This just uglifies the perfectly readable ascii.

> 
> Signed-off-by: Randy Dunlap <[rdunlap@infradead.org](mailto:rdunlap@infradead.org)>
> ---
> Cc: Jonathan Corbet <[corbet@lwn.net](mailto:corbet@lwn.net)>
> Cc: Shuah Khan <[skhan@linuxfoundation.org](mailto:skhan@linuxfoundation.org)>
> Cc: [linux-doc@vger.kernel.org](mailto:linux-doc@vger.kernel.org)
> Cc: Kees Cook <[kees@kernel.org](mailto:kees@kernel.org)>
> 
>  MAINTAINERS |   10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> --- linux-next-20260304.orig/MAINTAINERS
> +++ linux-next-20260304/MAINTAINERS
> @@ -32,10 +32,10 @@ Descriptions of section entries and pref
>  	   Type is one of: git, hg, quilt, stgit, topgit
>  	F: *Files* and directories wildcard patterns.
>  	   A trailing slash includes all files and subdirectory files.
> -	   F:	drivers/net/	all files in and below drivers/net
> -	   F:	drivers/net/*	all files in drivers/net, but not below
> -	   F:	*/net/*		all files in "any top level directory"/net
> -	   F:	fs/**/*foo*.c	all *foo*.c files in any subdirectory of fs
> +	   F:	``drivers/net/``  -	all files in and below drivers/net
> +	   F:	``drivers/net/*`` -	all files in drivers/net, but not below
> +	   F:	``*/net/*``       -	all files in "any top level directory"/net
> +	   F:	``fs/**/*foo*.c`` -	all *foo*.c files in any subdirectory of fs
>  	   One pattern per line.  Multiple F: lines acceptable.
>  	X: *Excluded* files and directories that are NOT maintained, same
>  	   rules as F:. Files exclusions are tested before file matches.
> @@ -44,7 +44,7 @@ Descriptions of section entries and pref
>  	   X:	net/ipv6/
>  	   matches all files in and below net excluding net/ipv6/
>  	N: Files and directories *Regex* patterns.
> -	   N:	[^a-z]tegra	all files whose path contains tegra
> +	   N:	[^a-z]tegra -	all files whose path contains tegra
>  	                        (not including files like integrator)
>  	   One pattern per line.  Multiple N: lines acceptable.
>  	   scripts/get_maintainer.pl has different behavior for files that
> 
> ```

  parent reply	other threads:[~2026-03-05  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 22:42 Randy Dunlap
2026-03-04 22:50 ` Jonathan Corbet
2026-03-05  0:24   ` Randy Dunlap
2026-03-05  9:24 ` Joe Perches [this message]
2026-03-05 21:26   ` Randy Dunlap

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=1d96c26a14026c7f914e95fba1af10e7a2726bda.camel@perches.com \
    --to=joe@perches.com \
    --cc=corbet@lwn.net \
    --cc=kees@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®