All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Jennings <ralph@oro.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Will LVM stay GPL?
Date: Thu, 6 Sep 2001 18:10:04 -0700	[thread overview]
Message-ID: <20010906181004.A10569@d3.front> (raw)
In-Reply-To: <20010906135502.B638@btconnect.com>

On Thu, Sep 06, 2001 at 01:55:02PM +0100, Joe Thornber wrote:
> Mike Declerck has already addressed this issue on the mailing list,
> but I'll reiterate.  The LVM kernel driver is GPL, the LVM userland
> tools are GPL.  We have no intention to change this, and even if we
> wanted to we couldn't since lots of people outside Sistina have
> contributed.
> 
> If it makes people feel happier I will accept patches that add their
> names to the copyright notices (assuming they've made significant
> contributions).

Besides, if they *do* decide to switch the licensing, all we have
to do is go back one revision and branch a new LVM project from the
GPL'd code.  So lets wait till that happens, then branch off an
OpenLVM project from the latest GPL released LVM code.  But untill
that happens who cares, they can't pull the carpet out from under
our feet untill they change the license, and untill they decide to
do that (if they decide to), all work is GPL'd, and they're doing a
great job of it.

IANAL of course, but I've been told that you can't make a license
change from GPL to anything else retroactive?!?!?

  -Ralph

  reply	other threads:[~2001-09-07  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 12:07 [linux-lvm] Will LVM stay GPL? Thomas Gebhardt
2001-09-06 12:46 ` Rob Latham
2001-09-06 12:55 ` Joe Thornber
2001-09-07  1:10   ` Ralph Jennings [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-08 19:22 Gonyou, Austin

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=20010906181004.A10569@d3.front \
    --to=ralph@oro.net \
    --cc=linux-lvm@sistina.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.