From: Andrew Morton <akpm@linux-foundation.org>
To: Jingoo Han <jg1.han@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fbdev@vger.kernel.org,
'Richard Purdie' <rpurdie@rpsys.net>,
'Thierry Reding' <thierry.reding@gmail.com>,
'Tomi Valkeinen' <tomi.valkeinen@ti.com>,
'Laurent Pinchart' <laurent.pinchart+renesas@ideasonboard.com>,
'Michael Hennerich' <michael.hennerich@analog.com>,
'Milo Kim' <milo.kim@ti.com>,
'Daniel Jeong' <gshark.jeong@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: remove Richard Purdie as backlight maintainer
Date: Fri, 04 Oct 2013 00:43:15 +0000 [thread overview]
Message-ID: <20131003174315.d9aa8af7.akpm@linux-foundation.org> (raw)
In-Reply-To: <003801cec093$6b3c1bf0$41b453d0$%han@samsung.com>
On Fri, 04 Oct 2013 08:50:57 +0900 Jingoo Han <jg1.han@samsung.com> wrote:
> On Friday, October 04, 2013 8:21 AM, Andrew Morton wrote:
> > On Fri, 27 Sep 2013 12:59:28 +0900 Jingoo Han <jg1.han@samsung.com> wrote:
> >
> > > Remove Richard Purdie as backlight subsystem maintainer, since he
> > > is not responding for a few years.
> >
> > It's nice to give a person a ./CREDITS entry when we remove them from
> > ./MAINTAINERS.
>
> However, Richard Purdie still remains as maintainers of other two entries
> as below:
> In this case, is it still necessary give him a ./CREDITS entry?
Necessary? No. Nice? Yes ;) I like to think that it reduces any of
the sting from being removed from MAINTAINERS. Plus it is more
accurate and costs nothing.
next prev parent reply other threads:[~2013-10-04 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 3:59 [PATCH] MAINTAINERS: remove Richard Purdie as backlight maintainer Jingoo Han
2013-10-03 23:20 ` Andrew Morton
2013-10-03 23:50 ` Jingoo Han
2013-10-04 0:43 ` Andrew Morton [this message]
2013-10-04 9:55 ` Richard Purdie
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=20131003174315.d9aa8af7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gshark.jeong@gmail.com \
--cc=jg1.han@samsung.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=milo.kim@ti.com \
--cc=rpurdie@rpsys.net \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).