From: Paul Jackson <pj@sgi.com>
To: Pat Gefre <pfg@sgi.com>
Cc: hch@infradead.org, linux-kernel@vger.kernel.org,
davidm@napali.hpl.hp.com
Subject: Re: [PATCH] Updating our sn code in 2.6
Date: Wed, 12 Nov 2003 18:42:33 -0800 [thread overview]
Message-ID: <20031112184233.2474003b.pj@sgi.com> (raw)
In-Reply-To: <Pine.SGI.3.96.1031112174709.40512D-100000@fsgi900.americas.sgi.com>
This patch still seems way too monolithic, Pat.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-11-13 2:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 23:31 [PATCH] Updating our sn code in 2.6 Pat Gefre
2003-11-07 10:25 ` Christoph Hellwig
2003-11-13 0:26 ` Pat Gefre
2003-11-13 2:42 ` Paul Jackson [this message]
2003-11-13 6:58 ` Christoph Hellwig
2003-11-13 16:48 ` Jesse Barnes
2003-11-14 12:10 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2003-12-19 2:59 Pat Gefre
2003-12-19 11:43 ` Christoph Hellwig
2003-12-20 0:35 ` Pat Gefre
2003-12-20 1:24 ` Jesse Barnes
2003-12-20 3:05 ` Jesse Barnes
2003-12-20 12:27 ` Christoph Hellwig
2003-12-23 2:55 ` Pat Gefre
2003-12-23 9:02 ` Christoph Hellwig
2003-12-23 14:46 ` Colin Ngam
2003-12-23 16:55 ` Christoph Hellwig
2003-12-26 19:42 ` Colin Ngam
2003-12-28 14:44 ` Christoph Hellwig
2003-12-28 16:32 ` Colin Ngam
2003-12-28 17:22 ` Christoph Hellwig
2003-12-29 1:10 ` Colin Ngam
2003-12-29 1:21 ` Colin Ngam
2003-12-28 14:36 ` Christoph Hellwig
2003-12-29 23:41 ` Jesse Barnes
2003-12-30 21:21 ` Pat Gefre
2003-12-30 21:24 ` Christoph Hellwig
2004-01-02 19:47 ` Patrick Gefre
2004-01-02 20:11 ` Christoph Hellwig
2004-03-29 15:39 ` Christoph Hellwig
2004-03-29 15:39 ` Patrick Gefre
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=20031112184233.2474003b.pj@sgi.com \
--to=pj@sgi.com \
--cc=davidm@napali.hpl.hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.