From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 3/5] MAINTAINERS.boards: add initial version
Date: Tue, 22 Apr 2014 10:05:20 +0200 [thread overview]
Message-ID: <E1WcVhi-0004og-2F@janus> (raw)
In-Reply-To: <20140422163032.3AE3.AA925319@jp.panasonic.com>
Hi Masahiro,
On Tue, 22 Apr 2014 16:30:32 +0900, Masahiro Yamada
<yamada.m@jp.panasonic.com> wrote:
> Hi Albert,
>
> > Can'we have the maintainer(s) be part of the board config file
> > from the start, like a required (but possible non-editable)
> > configuration item, something like "CONFIG_MAINTAINER_EMAIL"?
> >
> > This would, at least, keep all information for a single board
> > in a single place.
>
> I did this (CONFIG_BOARD_MAINTAINER) in my RFC
> http://patchwork.ozlabs.org/patch/330915/
> (but user-editable)
>
> I think everyone was opposed to my idea
> and we chose to add MAINTAINERS file.
I don't agree that everyone was opposed to it. There were disagreements
and suggestions to use get_maintainers.pl, and then disagreements about
this suggestion too.
(I did not chime in then for lack of time and because what I would have
said was already; I am chiming in now because Wolfgang was explicitly
wondering whether anyone was agreeing with him, and I am.)
I personally don't like the proposed MAINTAINERS format any more than I
liked the old one.
Also, I don't think we need a *centralized* source of information.
I think we need a source of information which requires minimal effort
when adding or removing a board (or SoC, or...). Therefore, I'm fine
with a board-specific file (defconfig or other) as long as it can be
recognized by (part of) its path and lives with the other board files.
> Best Regards
> Masahiro Yamada
Amicalement,
--
Albert.
next prev parent reply other threads:[~2014-04-22 8:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-20 20:57 [U-Boot] [RFC PATCH 0/5] introduce get_maintainer.pl Daniel Schwierzeck
2014-04-20 20:57 ` [U-Boot] [RFC PATCH 1/5] scripts: add script for converting boards.cfg to MAINTAINERS Daniel Schwierzeck
2014-04-20 20:57 ` [U-Boot] [RFC PATCH 2/5] MAINTAINERS: add initial version Daniel Schwierzeck
2014-04-20 21:22 ` Wolfgang Denk
2014-04-20 20:57 ` [U-Boot] [RFC PATCH 3/5] MAINTAINERS.boards: " Daniel Schwierzeck
2014-04-20 21:26 ` Wolfgang Denk
2014-04-21 18:46 ` Daniel Schwierzeck
2014-04-21 21:16 ` Wolfgang Denk
2014-04-22 6:42 ` Albert ARIBAUD
2014-04-22 7:30 ` Masahiro Yamada
2014-04-22 8:05 ` Albert ARIBAUD [this message]
2014-04-22 12:06 ` Wolfgang Denk
2014-04-22 12:01 ` Wolfgang Denk
2014-04-21 4:03 ` Masahiro Yamada
2014-04-21 9:19 ` Daniel Schwierzeck
2014-04-21 9:53 ` Masahiro Yamada
2014-04-20 20:57 ` [U-Boot] [RFC PATCH 4/5] get_maintainer.pl: import script from linux 3.14 Daniel Schwierzeck
2014-04-20 20:57 ` [U-Boot] [RFC PATCH 5/5] get_maintainer.pl: adapt to U-Boot tree Daniel Schwierzeck
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=E1WcVhi-0004og-2F@janus \
--to=albert.u.boot@aribaud.net \
--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 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.