From: Sean Young <sean@mess.org>
To: Hans Verkuil <hverkuil+cisco@kernel.org>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Ricardo Ribalda <ribalda@chromium.org>
Subject: Re: [PATCHv6 1/3] docs: media: update maintainer-entry-profile for multi-committers
Date: Tue, 28 Oct 2025 09:10:18 +0000 [thread overview]
Message-ID: <aQCIenbyRXm1e6J6@gofer.mess.org> (raw)
In-Reply-To: <8bc5196e-9a40-44da-941b-f5f42608c74f@kernel.org>
On Tue, Oct 28, 2025 at 09:25:29AM +0100, Hans Verkuil wrote:
> On 27/10/2025 23:06, Sean Young wrote:
> > On Mon, Oct 27, 2025 at 02:28:31PM +0100, Hans Verkuil wrote:
> >> From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> >>
> >> As the media subsystem will experiment with a multi-committers model,
> >> update the Maintainer's entry profile to the new rules.
> >>
> >> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> >> Reviewed-by: Ricardo Ribalda <ribalda@chromium.org>
> >> Signed-off-by: Hans Verkuil <hverkuil+cisco@kernel.org>
> >
> > I've read it and I only have some tiny nits, looks great.
>
> Thank you!
>
> >
> > Reviewed-by: Sean Young <sean@mess.org>
> >
>
> <snip>
>
> >> +It could be wise to also copy the Media Maintainer(s). You should use
> >> +``scripts/get_maintainers.pl`` to identify whom else needs to be copied.
> >> +Please always copy driver's authors and maintainers.
> >
> > git config for using scripts/get_maintainers.pl is useful
> I'm not sure I understand what you meant with this.
I should have been more specific. I use this in my .gitconfig:
[sendemail]
tocmd ="scripts/get_maintainer.pl --no-git --no-git-fallback --no-l --no-roles --no-rolestats"
cccmd ="scripts/get_maintainer.pl --no-git --no-git-fallback --no-m --no-roles --no-rolestats"
I find this very handy, I thought everyone was using this (possibly not).
Sean
next prev parent reply other threads:[~2025-10-28 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 13:28 [PATCHv6 0/3] docs: media: multicommitters model documentation Hans Verkuil
2025-10-27 13:28 ` [PATCHv6 1/3] docs: media: update maintainer-entry-profile for multi-committers Hans Verkuil
2025-10-27 22:06 ` Sean Young
2025-10-28 8:25 ` Hans Verkuil
2025-10-28 9:10 ` Sean Young [this message]
2025-10-27 13:28 ` [PATCHv6 2/3] docs: media: document media multi-committers rules and process Hans Verkuil
2025-10-27 13:28 ` [PATCHv6 3/3] docs: media: document Media Maintainers Hans Verkuil
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=aQCIenbyRXm1e6J6@gofer.mess.org \
--to=sean@mess.org \
--cc=bryan.odonoghue@linaro.org \
--cc=hverkuil+cisco@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=ribalda@chromium.org \
--cc=sakari.ailus@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).