From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/4] introduce get_maintainer.pl
Date: Thu, 04 Sep 2014 08:05:45 +0200 [thread overview]
Message-ID: <54080139.8090900@denx.de> (raw)
In-Reply-To: <CAPnjgZ1xnryV_V5pzK8COY_EH7P5M_1gJeeBKS-fPYaYPn3nHw@mail.gmail.com>
Hi Daniel,
On 04.09.2014 01:34, Simon Glass wrote:
>> This series imports get_maintainer.pl from kernel and reintroduce
>> the MAINTAINERS file in the according format. Currently one have to
>> manually grep all infos about board maintainers or custodians from
>> various sources like git log, wiki or boards.cfg. get_maintainer.pl
>> makes this task much easier. Also patman is already able to use it
>> for cc-cmd.
>>
>> The MAINTAINERS file contains all custodians and is hand-written based
>> on infos from wiki [1] and u-boot git forks [2]. Thus the source files
>> infos (F:) are not complete yet. Furthermore status (S:) and
>> maintainership (M:) for some custodian trees are probably wrong.
>> Any help in completing and fixing that is appreciated.
>>
>> The get_maintainers.pl script is modified to scan multiple
>> MAINTAINERS files in the board directory. This is required
>> with the switch to Kconfig which adds a MAINTAINERS file per board.
>>
>> Examples:
>>
>> $ ./scripts/get_maintainer.pl --nogit-fallback -f board/sandbox/
>> Simon Glass <sjg@chromium.org> (maintainer:SANDBOX BOARD)
>> u-boot at lists.denx.de (open list)
>>
>> $ ./scripts/get_maintainer.pl --nogit-fallback -f arch/sandbox/
>> Simon Glass <sjg@chromium.org> (maintainer:SANDBOX)
>> u-boot at lists.denx.de (open list)
>>
>> $ ./scripts/get_maintainer.pl --nogit-fallback -f board/sandburst/metrobox/
>> Travis Sawyer <travis.sawyer@sandburst.com> (orphan (since 2014-03):METROBOX BOARD)
>> u-boot at lists.denx.de (open list)
>>
>> This series is also available at git://git.denx.de/u-boot-mips.git/maintainers_v3.
>
> Patman now picks this up which is great. But it does sometimes produce
> a long list of maintainers. I wonder if we could have an option to
> turn it off (perhaps -m)?
Yes, that would be good. I just recently got a very long Cc list in my
quite bit patchset. This definitely was too much and I had to send those
patches manually instead of using patman. We need an option to disable this.
Thanks,
Stefan
next prev parent reply other threads:[~2014-09-04 6:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 0:24 [U-Boot] [PATCH v3 0/4] introduce get_maintainer.pl Daniel Schwierzeck
2014-08-01 0:24 ` [U-Boot] [PATCH v3 1/4] MAINTAINERS: add initial version Daniel Schwierzeck
2014-08-10 22:23 ` [U-Boot] [U-Boot,v3,1/4] " Tom Rini
2014-08-01 0:24 ` [U-Boot] [PATCH v3 2/4] get_maintainer.pl: import script from linux 3.15 Daniel Schwierzeck
2014-08-04 10:14 ` Simon Glass
2014-08-10 22:23 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-08-01 0:24 ` [U-Boot] [PATCH v3 3/4] get_maintainer.pl: adapt to U-Boot tree Daniel Schwierzeck
2014-08-10 22:23 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-08-01 0:24 ` [U-Boot] [PATCH v3 4/4] get_maintainer.pl: add support for scanning multiple MAINTAINERS files Daniel Schwierzeck
2014-08-10 22:23 ` [U-Boot] [U-Boot, v3, " Tom Rini
2014-09-03 23:34 ` [U-Boot] [PATCH v3 0/4] introduce get_maintainer.pl Simon Glass
2014-09-04 6:05 ` Stefan Roese [this message]
2014-09-04 13:05 ` Masahiro YAMADA
2014-09-04 20:45 ` Daniel Schwierzeck
2014-09-04 22:07 ` Simon Glass
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=54080139.8090900@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox