linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.
Date: Tue, 31 Jan 2017 12:55:26 -0800	[thread overview]
Message-ID: <7f2dfd64-0054-4b1f-fc13-a4d1912c05db@gmail.com> (raw)
In-Reply-To: <1485894779.25562.1.camel@crowfest.net>

On 01/31/2017 12:32 PM, Michael Zoran wrote:
> On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote:
>> I've been maintaining the bcm2835 branches here for a year or so.
>>
>> Signed-off-by: Eric Anholt <eric@anholt.net>
>> ---
>>  MAINTAINERS | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 844835563ef8..64b281a7ff09 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2624,7 +2624,7 @@ M:	Lee Jones <lee@kernel.org>
>>  M:	Eric Anholt <eric@anholt.net>
>>  L:	linux-rpi-kernel at lists.infradead.org (moderated for non-
>> subscribers)
>>  L:	linux-arm-kernel at lists.infradead.org (moderated for non-
>> subscribers)
>> -T:	git
>> git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git
>> +T:	git git://github.com/anholt/linux
>>  S:	Maintained
>>  N:	bcm283[5-7x]
>>  F:	drivers/staging/vc04_services
> 
> Just to add two cents here, since this is sort of a open source
> community driven thing, I think there should be multiple maintainers in
> case of a disagreement.  2 is good, 3 is better so that it's impossible
> to have a split disagreement and the third person can break the tie.

You may want to look at the file, and not the diff, which is already
listing 3 people.

> 
> Github is cool as the e-mail based system is really, really bad.  But
> if it is on github, I think it should have a neutral name not a
> person's name and allow multiple people to merge in pulls.
> 
> Unless of course, Eric wants to take 100% control of this whole thing.
> 

Really not clear what point you are trying to make here, other than you
may not like how things are, but at some point, someone needs to merge
patches somewhere, in a repository that's convenient, only to have them
pulled by whoever is next up in the food chain. Where the code is really
does not matter much because: git is distributed, patches can be
collected from mailing-list archives.
-- 
Florian

  parent reply	other threads:[~2017-01-31 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 19:48 [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree Eric Anholt
2017-01-31 20:32 ` Michael Zoran
2017-01-31 20:44   ` Russell King - ARM Linux
2017-01-31 20:55   ` Florian Fainelli [this message]
2017-01-31 21:10     ` Michael Zoran
2017-01-31 21:11 ` Stefan Wahren
2017-02-01  5:22 ` Stephen Warren
2017-02-01 22:14 ` Florian Fainelli

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=7f2dfd64-0054-4b1f-fc13-a4d1912c05db@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).