From: David Rientjes <rientjes@google.com>
To: lkml@think-future.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Documentation/cgroups/cpusets.txt author: Undelivered Mail Returned to Sender
Date: Sat, 20 Feb 2010 17:02:33 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002201700180.20140@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100220173449.GB19055@localhost>
On Sat, 20 Feb 2010, lkml@think-future.de wrote:
> Hi,
>
> The file Documentation/cgroups/cpusets.txt features an authors
> email address that seems outdated: Paul Jackson <pj@sgi.com>
>
> How should an authors email address that's no longer valid be
> replaced, so next time I'd send in a patch..
>
commit c222817f6add85197790e0071f6e511eff14ba25
Author: Paul Jackson <pj@sgi.com>
Date: Fri Oct 3 15:23:42 2008 -0700
cpusets: remove pj from cpuset maintainers
Remove myself from the kernel MAINTAINERS file for cpusets. I am leaving
SGI and probably will not be active in Linux kernel work. I can be
reached at <pj@usa.net>. Contact Derek Fults <dfults@sgi.com> for future
SGI+cpuset related issues. I'm off to the next chapter of this good life.
Signed-off-by: Paul Jackson <pj@sgi.com>
Cc: Paul Menage <menage@google.com>
Cc: Derek Fults <dfults@sgi.com>
Cc: John Hesterberg <jh@sgi.com>
Cc: Paul Jackson <pj@usa.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
scripts/get_maintainer.pl is a good pointer to who to cc on your patches:
$ ./scripts/get_maintainer.pl -f kernel/cpuset.c
Paul Menage <menage@google.com>
Andrew Morton <akpm@linux-foundation.org>
Li Zefan <lizf@cn.fujitsu.com>
Ingo Molnar <mingo@elte.hu>
Miao Xie <miaox@cn.fujitsu.com>
linux-kernel@vger.kernel.org
prev parent reply other threads:[~2010-02-21 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 17:34 lkml
2010-02-21 1:02 ` David Rientjes [this message]
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=alpine.DEB.2.00.1002201700180.20140@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@think-future.de \
/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
all inboxes | Powered by JetHome®