linux-kernel - Re: [PATCH] MAINTAINERS: Update for the current location of the bcm2835 tree.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1485894779.25562.1.camel@crowfest.net>
Date:   Tue, 31 Jan 2017 12:32:59 -0800
From:   Michael Zoran <mzoran@...wfest.net>
To:     Eric Anholt <eric@...olt.net>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     Lee Jones <lee@...nel.org>, linux-kernel@...r.kernel.org,
        bcm-kernel-feedback-list@...adcom.com,
        linux-rpi-kernel@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Update for the current location of the
 bcm2835 tree.

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@...olt.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@...nel.org>
>  M:	Eric Anholt <eric@...olt.net>
>  L:	linux-rpi-kernel@...ts.infradead.org (moderated for non-
> subscribers)
>  L:	linux-arm-kernel@...ts.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. 

Unless of course, Eric wants to take 100% control of this whole thing.