From: Jens Axboe <axboe@suse.de>
To: Rory Browne <robro@compsoc.nuigalway.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BK Licence: Protocols and Research
Date: Thu, 17 Jul 2003 14:35:14 +0200 [thread overview]
Message-ID: <20030717123514.GP833@suse.de> (raw)
In-Reply-To: <20030717120505.GA22304@zion.nuigalway.ie>
On Thu, Jul 17 2003, Rory Browne wrote:
> Hi
>
> I don't mean to start/restart/prolong a flame war about Bitkepper, but,
> I have a few things I'd like to have clarified.
Then keep it away from lkml? Why does everybody think that BK
discussions belong here?! News flash: they don't!
--
Jens Axboe
next prev parent reply other threads:[~2003-07-17 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 12:05 BK Licence: Protocols and Research Rory Browne
2003-07-17 12:15 ` Sean Neakums
2003-07-17 12:28 ` Alan Cox
2003-07-17 12:35 ` Jens Axboe [this message]
2003-07-17 13:39 ` Rory Browne
2003-07-17 14:09 ` Alan Cox
2003-07-17 14:58 ` Larry McVoy
2003-07-17 21:01 ` Rory Browne
2003-07-17 21:41 ` Mike Fedyk
2003-07-17 22:01 ` Larry McVoy
2003-07-18 3:01 ` jw schultz
2003-07-22 16:56 ` Jamie Lokier
2003-07-22 20:15 ` Brian McGroarty
2003-07-22 20:23 ` Jamie Lokier
2003-07-17 14:17 John Bradford
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=20030717123514.GP833@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robro@compsoc.nuigalway.ie \
/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;
as well as URLs for NNTP newsgroup(s).