From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Adam Fritzler <mid@zigamorph.net>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Jeff Garzik <jgarzik@pobox.com>,
Mike Phillips <mikep@linuxtr.net>,
Philip Blundell <philb@gnu.org>,
linux-scsi@vger.kernel.org, netdev@vger.kernel.org,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] MAINTAINERS: remove Adam Fritzler, update his email address in other sources
Date: Mon, 17 Dec 2007 20:28:00 -0800 [thread overview]
Message-ID: <20071217202800.1c898441.akpm@linux-foundation.org> (raw)
In-Reply-To: <1197951126.4891.13.camel@localhost>
On Mon, 17 Dec 2007 20:12:06 -0800 Joe Perches <joe@perches.com> wrote:
> Adam isn't a maintainer anymore.
> His old email address bounces.
> Update to new email address.
>
> On Mon, Dec 17, 2007 at 01:03:48PM -0800, Joe Perches wrote:
> > > You seem to have an old email address in the
> > > linux-kernel MAINTAINERS file.
> > > Should it be deleted or changed?
> On Mon, 2007-12-17 at 19:27 -0800, Adam Fritzler wrote:
> > I am no longer actively involved. If you can mark me as a former point
> > of contact, that's fine, or you can just delete the entry. My name is
> > still in the source, but with the old address. It'd great if the
> > address in source was updated.
>
> ...
>
> -TMS380 TOKEN-RING NETWORK DRIVER
> -P: Adam Fritzler
> -M: mid@auk.cx
> -L: linux-tr@linuxtr.net
> -W: http://www.auk.cx/tms380tr/
> -S: Maintained
>
> ...
>
> - * Added MCA support Adam Fritzler <mid@auk.cx>
> + * Added MCA support Adam Fritzler <mid@zigamorph.net>
This is fairly pointless - it'll just break again when Adam moves again.
Every problem can be solved with another layer of...
Please: just replace all instances with plain old "Adam Fritzler" and then
ensure that the lookup key "Adam Fritzler" has an accurate (and
non-duplicated anywhere else!) entry in MAINTAINERS or CREDITS or whatever.
btw, I cheerfully skipped all your spelling-fixes patches. Some will have
stuck via subsystem maintainers but I have a secret "no spelling fixes
unless they're end-user-visible" policy. That means I'll take spelling
fixes only if they're in printks or in Documentation/*. This is a little
defense mechanism to avoid getting buried in micropatches.
I'd suggest that you find out if Adrian is still running the trivial tree
and if so, patchbomb him.
next prev parent reply other threads:[~2007-12-18 4:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 4:12 [PATCH] MAINTAINERS: remove Adam Fritzler, update his email address in other sources Joe Perches
2007-12-18 4:28 ` Andrew Morton [this message]
2007-12-18 4:48 ` Joe Perches
2007-12-18 13:43 ` Matthew Wilcox
2007-12-18 16:40 ` Joe Perches
2007-12-22 8:44 ` Andrew Morton
2007-12-22 8:53 ` Jeff Garzik
2007-12-22 8:59 ` Joe Perches
2007-12-18 7:39 ` Adrian Bunk
2007-12-18 15:13 ` Arjan van de Ven
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=20071217202800.1c898441.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mid@zigamorph.net \
--cc=mikep@linuxtr.net \
--cc=netdev@vger.kernel.org \
--cc=philb@gnu.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).