From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/4] support/scripts/get-developers: add new script
Date: Wed, 21 Sep 2016 10:50:53 +0200 [thread overview]
Message-ID: <20160921105053.751ff924@free-electrons.com> (raw)
In-Reply-To: <87eg4dzqds.fsf@dell.be.48ers.dk>
Hello,
On Wed, 21 Sep 2016 09:03:11 +0200, Peter Korsgaard wrote:
> > A few files are recognized specially:
>
> > - .mk files are parsed, and if they contain $(eval
> > $(<something>-package)), the developer is assumed to be looking after
> > the corresponding package. This way, autobuilder failures for this
> > package can be reported directly to this developer.
>
> > - arch/Config.in.<arch> files are recognized as "the developer is
> > looking after the <arch> architecture". In this case, get-developer
> > parses the arch/Config.in.<arch> to get the list of possible BR2_ARCH
> > values. This way, autobuilder failures for this package can be
> > reported directly to this developer.
>
> > - pkg/pkg-<infra>.mk are recognized as "the developer is looking after
> > the <infra> package infrastructure. In this case, any patch that adds
> > or touches a .mk file that uses this infrastructure will be sent to
> > this developer.
>
> Committed, thanks. Care to send a followup patch fixing the issues
> Arnout pointed out?
Yes. I already started working on some of them. However, some
suggestions from Arnout are not working directly, especially the
argparse related suggestions around using mutually exclusive groups.
Patches from Arnout welcome :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-21 8:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 20:54 [Buildroot] [PATCH v3 0/4] Add a get-developers script and database Thomas Petazzoni
2016-09-12 20:54 ` [Buildroot] [PATCH v3 1/4] support/scripts/get-developers: add new script Thomas Petazzoni
2016-09-15 20:28 ` Arnout Vandecappelle
2016-09-21 7:03 ` Peter Korsgaard
2016-09-21 8:50 ` Thomas Petazzoni [this message]
2016-09-21 9:25 ` Arnout Vandecappelle
2016-09-12 20:54 ` [Buildroot] [PATCH v3 2/4] DEVELOPERS: add initial list of Buildroot developers Thomas Petazzoni
2016-09-21 7:04 ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 3/4] docs/manual: update contribute.txt to cover get-developers Thomas Petazzoni
2016-09-12 21:09 ` Yann E. MORIN
2016-09-15 20:29 ` Arnout Vandecappelle
2016-09-21 7:07 ` Peter Korsgaard
2016-09-12 20:54 ` [Buildroot] [PATCH v3 4/4] docs/manual: add new section about the DEVELOPERS file and get-developer Thomas Petazzoni
2016-09-15 20:35 ` Arnout Vandecappelle
2016-09-21 7:17 ` Peter Korsgaard
2016-09-12 21:14 ` [Buildroot] [PATCH v3 0/4] Add a get-developers script and database Yann E. MORIN
2016-09-12 21:30 ` Thomas Petazzoni
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=20160921105053.751ff924@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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