linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rory Browne <robro@compsoc.nuigalway.ie>
To: linux-kernel@vger.kernel.org
Subject: BK Licence: Protocols and Research
Date: Thu, 17 Jul 2003 13:05:05 +0100	[thread overview]
Message-ID: <20030717120505.GA22304@zion.nuigalway.ie> (raw)

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.

Would the conduction of research(and publication of results of same) on 
the bitkeeper formats/protocols, preclude users from using the Free version 
of Bitkeeper, for the research project?

Would the carrying out of such research using the free version of
Bitkeeper, prevent them from developing a product which contains
substantially similar capabilities of the BitKeeper Software in the
Future, assuming that all copies of Bitkeeper were destroyed before the
development started?

Would previous activity in the area of developing a product which
contains substantially similary features to Bitkeeper preclude users from
using the Free Bitkeeper software?

I apologise if you consider that this post would be better placed on a
different mailing list, but I felt I could get the most fulfilling
unbiased, and educational feedback here. 

Regards 

Rory

             reply	other threads:[~2003-07-17 11:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 12:05 Rory Browne [this message]
2003-07-17 12:15 ` BK Licence: Protocols and Research Sean Neakums
2003-07-17 12:28 ` Alan Cox
2003-07-17 12:35 ` Jens Axboe
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=20030717120505.GA22304@zion.nuigalway.ie \
    --to=robro@compsoc.nuigalway.ie \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).