From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] filter function for submaintainers
Date: Wed, 6 Apr 2011 21:34:16 +0200 [thread overview]
Message-ID: <20110406193416.GB767@pengutronix.de> (raw)
In-Reply-To: <20110406190313.GA767@pengutronix.de>
Hello,
at Pengutronix we think about using patchwork for the imx maintenance of
the kernel. (That is all related to arch/arm/{mach-{imx,mx*},plat-mxc}.)
The problem (admittedly only from a quick glance at
patchwork.ozlabs.org) I see is that it's not possible to reliably filter
patches by directory name. (Or maybe I'm just to stupid to find the
right knob, I tried searching for "drivers/net/ehea" in the netdev
project, got a few hits, but e.g.
http://patchwork.ozlabs.org/patch/89837/ wasn't listed. My guess is that
the search only checks subject and commit log?)
For us I think this is a crucial function, because the imx patches are
usually sent to the linux-arm-kernel mailing list where most patches
don't touch the files we are responsible for.
The obvious way to work around that problem is to set up a private
instance of patchwork and use procmail filtering to only feed it with
the "interesting" patches. Alternatively we have to convince enough
people to use the same instance such that only a few patches are left
without a responsible person. These few could then be
marked/deleted/whatever by many people and won't be a big problem.
Actually I would prefer a public instance that collects all patches from
the linux-arm-kernel mailing list. So it would be really great to have
such a filter.
Do you consider that a good feature? Would it be possible to get that
online on patchwork.ozlabs.org and let that instance host a
linux-arm-kernel project? (Assuming someone is willing to implement it
first.) I have to talk to my boss first and check with him if I can
invest some time to implement that, but if someone else volunteers to do
it, that would be fine for me, too.
(I wrote "we" through the mail, actually I'm not the maintainer of imx,
I just did one round of collecting patches recently and I'm already
annoyed.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next parent reply other threads:[~2011-04-06 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110404161716.GG13963@pengutronix.de>
[not found] ` <20110404170049.GA12200@pengutronix.de>
[not found] ` <20110404170515.GF7285@pengutronix.de>
[not found] ` <20110406190313.GA767@pengutronix.de>
2011-04-06 19:34 ` Uwe Kleine-König [this message]
2011-04-07 2:00 ` [RFC] filter function for submaintainers Jeremy Kerr
2011-04-07 7:38 ` Uwe Kleine-König
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=20110406193416.GB767@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).