public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Kconfig:  MAINTAINERS file or not?
Date: Tue, 06 May 2014 12:38:35 -0600	[thread overview]
Message-ID: <53692C2B.70009@wwwdotorg.org> (raw)
In-Reply-To: <20140506183303.GY22182@bill-the-cat>

On 05/06/2014 12:33 PM, Tom Rini wrote:
...
> An issue with a single top-level MAINTAINERS file is that we'll get
> conflicts galore.  What a MAINTAINERS file would give us is
> get_maintainers.pl from the kernel which can be helpful.

The conflicts we'll get are likely to be quite trivial to resolve though.

All changes to a particular entry should go through the subsystem tree
that the entry applies to (e.g. only the USB tree should change a
top-level USB entry, only an architecture or SoC tree should change an
entry for drivers for that architecture/SoC, etc.)

As such, it's pretty unlikely there will be many conflicts at all except
a few trivial context changes, or some add/add, add/delete conflicts of
adjacent blocks. I haven't see Linus complaining about issues merging
MAINTAINERS at all, and he'd complain if it was a problem.

Or, you could just say "all MAINTAINERS changes go through u-boot.git
directly". Then, there will be zero conflicts.

  reply	other threads:[~2014-05-06 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  9:58 [U-Boot] [RFC] Kconfig: MAINTAINERS file or not? Masahiro Yamada
2014-04-28 20:41 ` Wolfgang Denk
2014-04-30  5:31   ` Masahiro Yamada
2014-04-30 11:52     ` Andreas Bießmann
2014-04-30 16:21       ` Wolfgang Denk
2014-05-06 18:33 ` Tom Rini
2014-05-06 18:38   ` Stephen Warren [this message]
2014-05-06 20:09   ` Wolfgang Denk

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=53692C2B.70009@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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