From: Dean Nelson <dcn@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 3/4] SGI Altix cross partition functionality
Date: Thu, 17 Jun 2004 19:42:41 +0000 [thread overview]
Message-ID: <20040617194241.GA4060@sgi.com> (raw)
In-Reply-To: <20040617183638.GA3712@sgi.com>
On Thu, Jun 17, 2004 at 08:22:29PM +0100, Christoph Hellwig wrote:
> We already told you not to do this yesterday. Als please make all that
>
This [PATCH 3/4] was sent as one text file yesterday along with the others.
It never made it because of its size. So I resent it today as a gzip'd
attachment. I didn't mean for it to represent a response to any of
the comments I've received at this point.
At the moment I'm digesting the feedback and figuring out how to make
the necessary changes required to get this accepted by the community.
Thanks,
Dean
next prev parent reply other threads:[~2004-06-17 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:36 [PATCH 3/4] SGI Altix cross partition functionality Dean Nelson
2004-06-17 19:22 ` Christoph Hellwig
2004-06-17 19:42 ` Dean Nelson [this message]
2004-06-22 18:17 ` Dean Nelson
2004-06-22 18:26 ` Christoph Hellwig
2004-07-07 19:40 ` Dean Nelson
2004-07-11 10:11 ` Christoph Hellwig
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=20040617194241.GA4060@sgi.com \
--to=dcn@sgi.com \
--cc=linux-ia64@vger.kernel.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