From: Paul Jackson <pj@sgi.com>
To: "Paul Menage" <menage@google.com>
Cc: sekharan@us.ibm.com, akpm@osdl.org,
ckrm-tech@lists.sourceforge.net, linux-kernel@vger.kernel.org,
winget@google.com, mbligh@google.com, rohitseth@google.com,
jlan@sgi.com, Simon.Derr@bull.net
Subject: Re: [RFC][PATCH 0/4] Generic container system
Date: Tue, 3 Oct 2006 21:43:29 -0700 [thread overview]
Message-ID: <20061003214329.222440b6.pj@sgi.com> (raw)
In-Reply-To: <6599ad830610031934s41994158o59f1a2e58b1cb45e@mail.gmail.com>
Paul M wrote:
> The filesystem was lifted straight from cpuset.c,
The primary author of the cpuset file system code was Simon Derr.
I'd encourage you to include him on the cc list of future posts of
this patch set.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2006-10-04 4:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 9:53 [RFC][PATCH 0/4] Generic container system Paul Menage
2006-10-02 9:53 ` [RFC][PATCH 1/4] Generic container system abstracted from cpusets code Paul Menage
2006-10-02 9:53 ` [RFC][PATCH 2/4] Cpusets hooked into containers Paul Menage
2006-10-02 9:53 ` [RFC][PATCH 3/4] Add generic multi-subsystem API to containers Paul Menage
2006-10-02 9:53 ` [RFC][PATCH 4/4] Simple CPU accounting container subsystem Paul Menage
2006-10-04 1:35 ` [RFC][PATCH 0/4] Generic container system Chandra Seetharaman
2006-10-04 2:34 ` Paul Menage
2006-10-04 4:43 ` Paul Jackson [this message]
2006-10-04 18:56 ` Chandra Seetharaman
2006-10-04 19:36 ` Martin Bligh
2006-10-04 21:37 ` Chandra Seetharaman
2006-10-04 21:42 ` Paul Menage
2006-10-04 21:40 ` Paul Menage
2006-10-04 21:49 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2006-09-28 10:40 menage
2006-09-28 18:49 ` Paul Jackson
2006-09-28 19:00 ` Paul Menage
2006-09-29 4:31 ` Paul Jackson
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=20061003214329.222440b6.pj@sgi.com \
--to=pj@sgi.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=jlan@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=menage@google.com \
--cc=rohitseth@google.com \
--cc=sekharan@us.ibm.com \
--cc=winget@google.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