public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jeroen Hofstee <dasuboot@myspectrum.nl>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 1/4] MAINTAINERS: add initial version
Date: Sun, 27 Jul 2014 20:25:17 +0200	[thread overview]
Message-ID: <53D5440D.2020004@myspectrum.nl> (raw)
In-Reply-To: <CACUy__UgsxmaWqSQQHLk8rziVt+zwcrXHRHQyahaKT1w4mJgZA@mail.gmail.com>

Hello Daniel,

On 26-07-14 22:50, Daniel Schwierzeck wrote:
> Hi Jeroen,
>
> 2014-07-26 21:39 GMT+02:00 Jeroen Hofstee <dasuboot@myspectrum.nl>:
>> Hello Daniel,
>>
>>
>> On 26-07-14 20:54, Daniel Schwierzeck wrote:
>>> MAINTAINERS contains all currently known custodians based on
>>> infos from wiki [1] and u-boot git forks [2].
>>>
>>> [1] http://www.denx.de/wiki/U-Boot/Custodians
>>> [2] http://git.denx.de/?p=u-boot.git;a=forks
>>>
>>> Signed-off-by: Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
>>> ---
>>>
>>>    MAINTAINERS | 338
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>    1 file changed, 338 insertions(+)
>>>    create mode 100644 MAINTAINERS
>>>
>> huh, has this not already been refused several times in the past?
>>
> according to [1] we want to have one top-level MAINTAINERS for the
> custodians and multiple MAINTAINERS files per board (will be added
> with the Kconfig patch series)
>
> [1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/185242/focus=185899
>

Ah my bad, I interpreted this as yet another way to track maintainers.
But it seems you are at least aware the KConfig patchset also carry
such patches, so it likely is fine. Sorry for the noise.

Regards,
Jeroen

  reply	other threads:[~2014-07-27 18:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26 18:54 [U-Boot] [PATCH v1 0/4] introduce get_maintainer.pl Daniel Schwierzeck
2014-07-26 18:54 ` [U-Boot] [PATCH v1 1/4] MAINTAINERS: add initial version Daniel Schwierzeck
2014-07-26 19:39   ` Jeroen Hofstee
2014-07-26 20:50     ` Daniel Schwierzeck
2014-07-27 18:25       ` Jeroen Hofstee [this message]
2014-07-28  7:30   ` Michal Simek
2014-07-28 15:49     ` Tom Rini
2014-07-28  8:15   ` Ian Campbell
2014-07-28 14:03     ` Daniel Schwierzeck
2014-07-29  1:52   ` Masahiro Yamada
2014-07-29 11:52     ` Daniel Schwierzeck
2014-07-29 11:59   ` [U-Boot] [PATCH v2 " Daniel Schwierzeck
2014-07-30  6:27     ` Masahiro Yamada
2014-07-30  8:33     ` Masahiro Yamada
2014-07-30  9:02       ` Daniel Schwierzeck
2014-07-29 12:14   ` [U-Boot] [PATCH v1 " Stefano Babic
2014-07-29 12:29     ` Daniel Schwierzeck
2014-07-26 18:54 ` [U-Boot] [PATCH v1 2/4] get_maintainer.pl: import script from linux 3.15 Daniel Schwierzeck
2014-07-30 13:52   ` Simon Glass
2014-07-31 23:20     ` Daniel Schwierzeck
2014-08-04 10:14       ` Simon Glass
2014-07-26 18:54 ` [U-Boot] [PATCH v1 3/4] get_maintainer.pl: adapt to U-Boot tree Daniel Schwierzeck
2014-07-30 13:53   ` Simon Glass
2014-07-26 18:54 ` [U-Boot] [PATCH v1 4/4] get_maintainer.pl: add support for scanning multiple MAINTAINERS files 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=53D5440D.2020004@myspectrum.nl \
    --to=dasuboot@myspectrum.nl \
    --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