From: Nikita Danilov <nikita@clusterfs.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Gerrit Huizenga <gh@us.ibm.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
Rik van Riel <riel@redhat.com>, Chris Mason <mason@suse.com>,
ckrm-tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [PATCH] CKRM: 0/10 Class Based Kernel Resource Management
Date: Tue, 30 Nov 2004 11:55:52 +0300 [thread overview]
Message-ID: <m11xebd8br.fsf@clusterfs.com> (raw)
In-Reply-To: <20041129223251.GA12192@infradead.org> (Christoph Hellwig's message of "Mon, 29 Nov 2004 22:32:51 +0000")
Christoph Hellwig <hch@infradead.org> writes:
[...]
>
> And where's the people who wrote the code? Are people at IBM really
> all anxious cowards these days that can't submit their own code but have
> to abuse a highlevel manager for it.
Once upon a time everybody and his dog (old dogs and puppies alike) at
namesys used to send patches directly to Linus. Which resulted in the
latter being confused in a maze of @namesys.com addresses all similar,
and so he asked Hans to send all patches to him from Hans' address.
Nikita.
next prev parent reply other threads:[~2004-11-30 8:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:44 [PATCH] CKRM: 0/10 Class Based Kernel Resource Management Gerrit Huizenga
2004-11-29 20:23 ` Andrew Morton
2004-11-29 22:33 ` Gerrit Huizenga
2004-12-03 11:54 ` [ckrm-tech] " Marc E. Fiuczynski
2004-12-04 0:40 ` Andrew Morton
2004-12-04 8:33 ` Gerrit Huizenga
2004-12-06 6:30 ` Andrew Morton
2004-11-29 22:32 ` Christoph Hellwig
2004-11-29 22:51 ` Gerrit Huizenga
2004-11-30 8:55 ` Nikita Danilov [this message]
2004-11-30 2:43 ` Greg KH
2004-11-30 2:48 ` Gerrit Huizenga
2004-11-30 4:07 ` Greg KH
2004-11-30 5:59 ` Gerrit Huizenga
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=m11xebd8br.fsf@clusterfs.com \
--to=nikita@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=riel@redhat.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