From: Paul Bolle <pebolle@tiscali.nl>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul Mundt <paul.mundt@gmail.com>,
Magnus Damm <magnus.damm@gmail.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Simon Horman <horms@verge.net.au>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH RFC] MAINTAINERS: Mark SuperH orphan
Date: Sun, 16 Feb 2014 21:16:49 +0000 [thread overview]
Message-ID: <1392585409.28866.94.camel@x220> (raw)
In-Reply-To: <1392584137-24486-1-git-send-email-geert@linux-m68k.org>
On Sun, 2014-02-16 at 21:55 +0100, Geert Uytterhoeven wrote:
> From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
>
> Paul Mundt's email address bounces regularly, and he hasn't taken any
> SuperH patches for about one year.
>
> Suggested-by: Paul Bolle <pebolle@tiscali.nl>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
> ---
> MAINTAINERS | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
I think Andrew prefers to add an entry in CREDITS when removing someone
from MAINTAINERS. As that is the courteous thing to do, I guess.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b2cf5cfb4d29..2d294561ebdc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8372,12 +8372,10 @@ S: Maintained
> F: drivers/net/ethernet/dlink/sundance.c
>
> SUPERH
> -M: Paul Mundt <lethal@linux-sh.org>
> L: linux-sh@vger.kernel.org
> W: http://www.linux-sh.org
> Q: http://patchwork.kernel.org/project/linux-sh/list/
> -T: git git://github.com/pmundt/linux-sh.git sh-latest
> -S: Supported
> +S: Orphan
> F: Documentation/sh/
> F: arch/sh/
> F: drivers/sh/
Paul Bolle
next prev parent reply other threads:[~2014-02-16 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 20:55 [PATCH RFC] MAINTAINERS: Mark SuperH orphan Geert Uytterhoeven
2014-02-16 21:16 ` Paul Bolle [this message]
2014-02-16 21:28 ` Geert Uytterhoeven
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=1392585409.28866.94.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=akpm@linux-foundation.org \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=paul.mundt@gmail.com \
/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