From: Linus Walleij <linus.walleij@linaro.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful
Date: Wed, 17 Jul 2019 18:05:41 +0200 [thread overview]
Message-ID: <CACRpkdbydfyx8LMG8FzCzAYsTP9n57K0yw9_04wgtDSjm+B3iQ@mail.gmail.com> (raw)
In-Reply-To: <20190717073130.GA1021@kunai>
On Wed, Jul 17, 2019 at 9:31 AM Wolfram Sang <wsa@the-dreams.de> wrote:
> Guys, I am just trying to better cope with an amount of patches I can't
> handle on my own currently.
Maintainers don't scale right? :/
What I tend to do is git log on whatever is affected by a patch
and then pick some people who touched the code recently
and just add them to CC and ask them to help. This is especially
nice with drivers as I can quickly see (by intuition) whether
they are doing some general cleanup or actually are running
and testing the hardware, even if they didn't sign up as
maintainers. Sometimes nudge them to maintain the stuff
they seem so intimate with by adding themselves to
MAINTAINERS. If it was a while since they did the changes
I often do git log and grep for their name as they often
just changed email address.
It would be really neat if get_maintainer could do this but I
think it requires real intelligence rather than pattern-matching.
Just my €0.01
Linus Walleij
next prev parent reply other threads:[~2019-07-17 16:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 14:27 [Ksummit-discuss] [MAINTAINERS SUMMIT] Keeping reviews meaningful Wolfram Sang
2019-07-06 16:52 ` Leon Romanovsky
2019-07-06 17:17 ` Wolfram Sang
2019-07-08 10:47 ` Jan Kara
2019-07-08 11:47 ` Wolfram Sang
2019-07-15 16:11 ` Mauro Carvalho Chehab
2019-07-08 11:21 ` Geert Uytterhoeven
2019-07-08 11:59 ` Wolfram Sang
2019-07-15 15:58 ` Mauro Carvalho Chehab
2019-07-15 17:00 ` Theodore Y. Ts'o
2019-07-15 17:11 ` Mauro Carvalho Chehab
2019-07-16 21:26 ` Wolfram Sang
2019-08-17 21:35 ` Paul Walmsley
2019-08-19 6:57 ` Jan Kara
2019-08-19 7:06 ` Jiri Kosina
2019-08-19 7:06 ` Julia Lawall
2019-08-19 8:04 ` Jan Kara
2019-08-19 8:13 ` Julia Lawall
2019-08-20 10:22 ` James Bottomley
2019-08-19 8:26 ` Thomas Gleixner
2019-08-19 16:16 ` Christian Brauner
2019-08-19 19:04 ` Thomas Gleixner
2019-08-19 21:03 ` Christian Brauner
2019-07-08 14:57 ` Mark Brown
2019-07-14 9:35 ` Jonathan Cameron
2019-07-14 10:13 ` Thomas Gleixner
2019-07-15 9:10 ` Rafael J. Wysocki
2019-07-16 21:16 ` Wolfram Sang
2019-07-16 21:57 ` Olof Johansson
2019-07-16 22:27 ` Thomas Gleixner
2019-07-17 3:59 ` Randy Dunlap
2019-07-17 7:31 ` Wolfram Sang
2019-07-17 16:05 ` Linus Walleij [this message]
2019-07-17 16:40 ` Wolfram Sang
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=CACRpkdbydfyx8LMG8FzCzAYsTP9n57K0yw9_04wgtDSjm+B3iQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=wsa@the-dreams.de \
/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.