All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.
Date: Tue, 31 Jan 2017 20:44:51 +0000	[thread overview]
Message-ID: <20170131204451.GD27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1485894779.25562.1.camel@crowfest.net>

On Tue, Jan 31, 2017 at 12:32:59PM -0800, Michael Zoran wrote:
> On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote:
> > 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.
> 
> 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. 

The email-based "system" is standard Linux policy for patch review,
which has been established as a way of minimising the effort otherwise
required by reviewers.

If folk want to deal with stuff "internally" on github off-list, that's
fine, but in order to get patches upstreamed, the patches still need to
be posted to a public Linux mailing list for review purposes.

You can't get away from the "e-mail based system".  Sorry.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Michael Zoran <mzoran@crowfest.net>
Cc: Eric Anholt <eric@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Lee Jones <lee@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.
Date: Tue, 31 Jan 2017 20:44:51 +0000	[thread overview]
Message-ID: <20170131204451.GD27312@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1485894779.25562.1.camel@crowfest.net>

On Tue, Jan 31, 2017 at 12:32:59PM -0800, Michael Zoran wrote:
> On Tue, 2017-01-31 at 11:48 -0800, Eric Anholt wrote:
> > 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@lists.infradead.org (moderated for non-
> > subscribers)
> >  L:	linux-arm-kernel@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.
> 
> 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. 

The email-based "system" is standard Linux policy for patch review,
which has been established as a way of minimising the effort otherwise
required by reviewers.

If folk want to deal with stuff "internally" on github off-list, that's
fine, but in order to get patches upstreamed, the patches still need to
be posted to a public Linux mailing list for review purposes.

You can't get away from the "e-mail based system".  Sorry.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

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

Thread overview: 16+ 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 19:48 ` Eric Anholt
2017-01-31 20:32 ` Michael Zoran
2017-01-31 20:32   ` Michael Zoran
2017-01-31 20:44   ` Russell King - ARM Linux [this message]
2017-01-31 20:44     ` Russell King - ARM Linux
2017-01-31 20:55   ` Florian Fainelli
2017-01-31 20:55     ` Florian Fainelli
2017-01-31 21:10     ` Michael Zoran
2017-01-31 21:10       ` Michael Zoran
2017-01-31 21:11 ` Stefan Wahren
2017-01-31 21:11   ` Stefan Wahren
2017-02-01  5:22 ` Stephen Warren
2017-02-01  5:22   ` Stephen Warren
2017-02-01 22:14 ` Florian Fainelli
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=20170131204451.GD27312@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --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 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.