Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 5/5] DEVELOPERS: add me as a co-maintainer for rk3399 based targets
Date: Wed, 18 Mar 2020 21:52:16 +0100	[thread overview]
Message-ID: <20200318215216.187d07bd@windsurf.home> (raw)
In-Reply-To: <CAMty3ZBU8AP8SEuQC95eRELA5XZa2Dr92Efj3e3FENW24BiPfA@mail.gmail.com>

Hello Jagan,

On Wed, 18 Mar 2020 22:37:30 +0530
Jagan Teki <jagan@amarulasolutions.com> wrote:

> Doesn't it have a possibility of co-developer concept in buildroot
> like we do have linux maintainers file? I feel it makes sense to have
> it or the goal of this DEVELOPERS file seems different as what we
> think?

The Linux MAINTAINERS file and the Buildroot DEVELOPERS are organized
differently.

The Linux MAINTAINERS file is organized by topic/subsystem, and gives
for this subsystem the list of persons in charge of it.

The Buildroot DEVELOPERS is organized by person, and gives for each
person the list of packages/defconfigs/areas this person is interested
in.

It is unlikely that two different developers will have exactly the same
set of packages/defconfigs/areas they are interested in, so we don't
support having multiple name/e-mail in front of a single list of
packages/defconfigs. In addition, that would break the alphabetic
ordering of the file.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2020-03-18 20:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 10:44 [Buildroot] [PATCH v2 0/4] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board sunil at amarulasolutions.com
2020-02-13 10:44 ` [Buildroot] [PATCH v2 1/4] boot/arm-trusted-firmware: Disable bin copy for rk3399 sunil at amarulasolutions.com
2020-03-18 13:45   ` [Buildroot] [PATCH v3 0/5] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board sunil at amarulasolutions.com
2020-03-18 13:45     ` [Buildroot] [PATCH v3 1/5] boot/arm-trusted-firmware: Disable bin copy for rk3399 sunil at amarulasolutions.com
2020-03-18 13:45     ` [Buildroot] [PATCH v3 2/5] package/arm-gnu-a-toolchain: new package sunil at amarulasolutions.com
2020-03-18 13:45     ` [Buildroot] [PATCH v3 3/5] boot/arm-trusted-firmware: add support for rockchip rk3399 sunil at amarulasolutions.com
2020-03-18 13:45     ` [Buildroot] [PATCH v3 4/5] configs/roc-rk3399-pc: new defconfig sunil at amarulasolutions.com
2020-03-18 13:45     ` [Buildroot] [PATCH v3 5/5] DEVELOPERS: add me as a co-maintainer for rk3399 based targets sunil at amarulasolutions.com
2020-03-18 14:51       ` Heiko Thiery
2020-03-18 17:07         ` Jagan Teki
2020-03-18 18:05           ` Heiko Thiery
2020-03-18 20:52           ` Thomas Petazzoni [this message]
2020-03-19 10:46             ` [Buildroot] [PATCH v4 0/4] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board sunil at amarulasolutions.com
2020-03-19 10:46               ` [Buildroot] [PATCH v4 1/4] boot/arm-trusted-firmware: Disable bin copy for rk3399 sunil at amarulasolutions.com
2020-03-20 22:13                 ` Thomas Petazzoni
2020-03-19 10:46               ` [Buildroot] [PATCH v4 2/4] package/arm-gnu-a-toolchain: new package sunil at amarulasolutions.com
2020-03-19 10:46               ` [Buildroot] [PATCH v4 3/4] boot/arm-trusted-firmware: add support for rockchip rk3399 sunil at amarulasolutions.com
2020-03-20 22:14                 ` Thomas Petazzoni
2020-03-19 10:46               ` [Buildroot] [PATCH v4 4/4] configs/roc-rk3399-pc: new defconfig sunil at amarulasolutions.com
2020-02-13 10:44 ` [Buildroot] [PATCH v2 2/4] package/arm-gnu-a-toolchain: new package sunil at amarulasolutions.com
2020-02-14 12:32   ` Michael Walle
2020-02-16 23:28     ` Thomas Petazzoni
2020-02-13 10:44 ` [Buildroot] [PATCH v2 3/4] boot/arm-trusted-firmware: add support for rockchip rk3399 sunil at amarulasolutions.com
2020-02-13 10:44 ` [Buildroot] [PATCH v2 4/4] configs/roc-rk3399-pc: new defconfig sunil at amarulasolutions.com
2020-02-24  9:22   ` Jagan Teki
  -- strict thread matches above, loose matches on Subject: below --
2020-03-18 13:30 [Buildroot] [PATCH v3 0/5] Fix ATF v2.2 build for rk3399, add roc-rk3399-pc board sunil at amarulasolutions.com
2020-03-18 13:30 ` [Buildroot] [PATCH v3 5/5] DEVELOPERS: add me as a co-maintainer for rk3399 based targets sunil at amarulasolutions.com
2020-03-18 13:44   ` Sunil Kumar Mahesh

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=20200318215216.187d07bd@windsurf.home \
    --to=thomas.petazzoni@bootlin.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