From: Jon Masters <jonmasters@gmail.com>
To: "Jeff V. Merkey" <jmerkey@drdos.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Robert Love <rml@novell.com>,
Ankit Jain <ankitjain1580@yahoo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: processor affinity
Date: Wed, 29 Sep 2004 21:28:59 +0100 [thread overview]
Message-ID: <35fb2e590409291328458ebebd@mail.gmail.com> (raw)
In-Reply-To: <415B1064.1080302@drdos.com>
On Wed, 29 Sep 2004 13:43:32 -0600, Jeff V. Merkey <jmerkey@drdos.com> wrote:
> Since they are hiring as many top Linux folks as possible, and they have
> invested their entire future in Linux, I think their actions speak so loud,
I only asked because I'd not heard of an official patent position from
them (but I've not looked) and I wondered if someone happened to know
- words are completely meaningless.
<snip>
Wow, tha'ts one bitter mail you sent. Sorry to hear about it but I'd
rather not start a general discussion about big business practices and
Novell - just interested in the patent situation.
Jon.
next prev parent reply other threads:[~2004-09-29 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 12:25 processor affinity Ankit Jain
2004-09-28 13:39 ` Toon van der Pas
2004-09-28 13:47 ` Jon Masters
2004-09-28 13:55 ` Neil Horman
2004-09-28 14:04 ` Jeff V. Merkey
2004-09-28 15:58 ` Robert Love
2004-09-28 16:02 ` Jeff V. Merkey
2004-09-28 21:51 ` Alan Cox
2004-09-29 16:56 ` Jeff V. Merkey
2004-09-29 17:45 ` Christoph Hellwig
2004-09-29 19:24 ` Jeff V. Merkey
2004-09-29 20:08 ` Jon Masters
2004-09-29 19:43 ` Jeff V. Merkey
2004-09-29 20:28 ` Jon Masters [this message]
2004-09-29 20:03 ` Jeff V. Merkey
2004-09-30 2:39 ` Nick Piggin
[not found] ` <20040930124708.GA2520@galt.devicelogics.com>
2004-10-01 3:09 ` Nick Piggin
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=35fb2e590409291328458ebebd@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ankitjain1580@yahoo.com \
--cc=hch@infradead.org \
--cc=jmerkey@drdos.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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.