public inbox for cygwin-licensing@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-licensing@cygwin.com
Subject: Re: Cygwin now licensed under GPLv3+
Date: Tue, 13 Sep 2011 04:58:00 -0000	[thread overview]
Message-ID: <20110913045747.GB20347@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4E6ED010.7040300@cisra.canon.com.au>

On Tue, Sep 13, 2011 at 01:37:52PM +1000, Luke Kendall wrote:
>Corinna Vinschen wrote:
>> Hi Cygwin friends and users,
>>
>>
>> I'm happy to announce that, effective immediately, Red Hat has
>> relicensed Cygwin from "GNU Public License version 2" (GPLv2) to
>> "GNU Public License version 3 or later" (GPLv3+).
>>
>>   
>
>What does that mean in terms of Cygwin components?

Corinna referenced a page:

http://cygwin.com/licensing.html

which barely changed except to mention GPLv3.  This many-month old email
was just meant to announce that the Cygwin DLL and associated utilities
were moving from GPLv2 to GPLv3.

>Each component normally has its own license, so does the above
>statement mean that things like the Cygwin DLL and other Cygwin-only
>components are under GPLv3?

Red Hat did not suddenly assume the extralegal power to change the
licensing of other packages.

>Is there an explicit list or a precise description of what parts of 
>Cygwin are covered by GPLv3?

You mean like the very web page that you quoted below?

>> The Open Source Licensing Exception persists, as well as the
>> availability of the Cygwin Alternative License, as described on
>> http://cygwin.com/licensing.html

  reply	other threads:[~2011-09-13  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110419171444.GF23804@calimero.vinschen.de>
2011-09-13  4:44 ` Luke Kendall
2011-09-13  4:58   ` Christopher Faylor [this message]
2011-09-13 15:28     ` Luke Kendall
2011-09-13 15:38       ` Christopher Faylor
2011-10-20  7:35 Luke Kendall
2011-10-20  7:49 ` Corinna Vinschen

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=20110913045747.GB20347@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-licensing@cygwin.com \
    --cc=cygwin@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).