workflows.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Vlastimil Babka <vbabka@suse.cz>, Joe Perches <joe@perches.com>,
	 Andrew Morton <akpm@linux-foundation.org>,
	workflows@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	 Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	 Kees Cook <kees@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] get_maintainer: add --substatus for reporting subsystem status
Date: Wed, 12 Feb 2025 15:53:16 +0100	[thread overview]
Message-ID: <r53ilw7b2q7th2lru6f7dc4bpbrowivgb2cjr7ur3edl5dwhmr@qxtbdor5x73y> (raw)
In-Reply-To: <CAMuHMdWvTDO6wcLQs1DwrEjj3jDDav5uKU6E-5=TKFK9w1Nb-w@mail.gmail.com>

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

On Wed, Feb 12, 2025 at 01:42:15PM +0100, Geert Uytterhoeven wrote:
> Hi Vlastimil,
> 
> On Tue, 11 Feb 2025 at 17:01, Vlastimil Babka <vbabka@suse.cz> wrote:
> > On 2/3/25 12:13, Vlastimil Babka wrote:
> > > The subsystem status is currently reported with --role(stats) by
> > > adjusting the maintainer role for any status different from Maintained.
> > > This has two downsides:
> > >
> > > - if a subsystem has only reviewers or mailing lists and no maintainers,
> > >   the status is not reported (i.e. typically, Orphan subsystems have no
> > >   maintainers)
> > >
> > > - the Supported status means that someone is paid for maintaining, but
> > >   it is reported as "supporter" for all the maintainers, which can be
> > >   incorrect. People have been also confused about what "supporter"
> > >   means.
> > >
> > > This patch introduces a new --substatus option and functionality aimed
> > > to report the subsystem status separately, without adjusting the
> > > reported maintainer role. After the e-mails are output, the status of
> > > subsystems will follow, for example:
> > >
> > > ...
> > > linux-kernel@vger.kernel.org (open list:LIBRARY CODE)
> > > LIBRARY CODE status: Supported
> > >
> > > In order to allow replacing the role rewriting seamlessly, the new
> > > option works as follows:
> > >
> > > - it is automatically enabled when --email and --role are enabled
> > >   (the defaults include --email and --rolestats which implies --role)
> >
> > With the following fixup, the above changes to:
> >
> > - it is automatically enabled when --email and --role are enabled and the
> >   output is a terminal (the defaults include --email and --rolestats which
> >   implies --role)
> >
> > ----8<----
> > From f5523a85c742065fcb88a8aa26831f9dba9faf15 Mon Sep 17 00:00:00 2001
> > From: Vlastimil Babka <vbabka@suse.cz>
> > Date: Tue, 11 Feb 2025 16:16:11 +0100
> > Subject: [PATCH] get_maintainer: add --substatus for reporting subsystem
> >  status - fix
> >
> > The automatically enabled --substatus can break existing scripts that do
> > not disable --rolestats. Require that script output goes to a terminal
> > to enable it automatically.
> >
> > Signed-off-by: Vlastimil Babka <vbabka@suse.cz>
> 
> Thanks, that fixes the issue for me.
> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be>

Ditto for me (it allows me to undo the workaround I already implemented
:-)

Tested-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

To please the regzbot, you also might want to add:

Fixes: c1565b6f7b53 ("get_maintainer: add --substatus for reporting subsystem status")
Closes: https://lore.kernel.org/all/7aodxv46lj6rthjo4i5zhhx2lybrhb4uknpej2dyz3e7im5w3w@w23bz6fx3jnn/

Thanks
Uwe

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

  reply	other threads:[~2025-02-12 14:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03 11:13 [PATCH v2 0/2] get_maintainer: report subsystem status separately from maintainer role Vlastimil Babka
2025-02-03 11:13 ` [PATCH v2 1/2] get_maintainer: add --substatus for reporting subsystem status Vlastimil Babka
2025-02-04 10:19   ` Lorenzo Stoakes
2025-02-11 10:32   ` Uwe Kleine-König
2025-02-11 10:48     ` Geert Uytterhoeven
2025-02-11 10:59       ` Vlastimil Babka
2025-02-11 11:05         ` Vlastimil Babka
2025-02-11 15:19         ` Geert Uytterhoeven
2025-02-11 15:30           ` Vlastimil Babka
2025-02-11 16:28             ` Geert Uytterhoeven
2025-02-11 18:39               ` Vlastimil Babka
2025-02-11 15:09       ` Uwe Kleine-König
2025-02-11 15:22         ` Geert Uytterhoeven
2025-02-11 15:20   ` Vlastimil Babka
2025-02-12 12:42     ` Geert Uytterhoeven
2025-02-12 14:53       ` Uwe Kleine-König [this message]
2025-02-03 11:13 ` [PATCH v2 2/2] get_maintainer: stop reporting subsystem status as maintainer role Vlastimil Babka
2025-02-04 10:18   ` Lorenzo Stoakes
2025-02-04 10:12 ` [PATCH v2 0/2] get_maintainer: report subsystem status separately from " Lorenzo Stoakes

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=r53ilw7b2q7th2lru6f7dc4bpbrowivgb2cjr7ur3edl5dwhmr@qxtbdor5x73y \
    --to=u.kleine-koenig@baylibre.com \
    --cc=akpm@linux-foundation.org \
    --cc=bryan.odonoghue@linaro.org \
    --cc=geert@linux-m68k.org \
    --cc=joe@perches.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=tytso@mit.edu \
    --cc=vbabka@suse.cz \
    --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