public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ronald Landheer" <info@rlsystems.net>
To: "David Starks-Browning" <starksb@ebi.ac.uk>, <cygwin@cygwin.com>
Subject: RE: How to distribute programs compiled on cygwin? FAQ alert
Date: Sat, 22 Sep 2001 06:27:00 -0000	[thread overview]
Message-ID: <NFBBLOMHALONCDMPGBLFAEBCCCAA.info@rlsystems.net> (raw)
In-Reply-To: <943-Sat22Sep2001095135+0100-starksb@ebi.ac.uk>

Hi David,

>>> I've a little bone to pick: It's not consistent with the
>>> licensing.html page which permits any opensource license, not just
>>> the GPL. This will likely create confusion.
>> Nice catch, Robert.  I missed this.
> Sorry!  Here's what is in the FAQ now:
>     ... Unless you purchase a special commercial license from Red Hat,
>     then your software must comply with the Open Source Definition or
>     the GPL.
I'd make it ".. with the Open Source Definition, like the GPL."
                                                 ^^^^
Otherwise, ye might think GPL doesn't conform to the Open Source 
Definition..

Greetz!

Ronald


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2001-09-22  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 16:08 How to distribute programs compiled on cygwin? Srinivas Kommu
2001-09-03 18:02 ` How to distribute programs compiled on cygwin? FAQ alert Christopher Faylor
2001-09-08 10:21   ` David Starks-Browning
2001-09-21 11:26   ` David Starks-Browning
2001-09-21 11:28     ` Christopher Faylor
2001-09-21 17:28       ` Robert Collins
2001-09-21 18:12         ` Christopher Faylor
2001-09-22  1:51           ` David Starks-Browning
2001-09-22  6:13             ` Adrian Phillips
2001-09-22  6:27             ` Ronald Landheer [this message]
2001-09-22 12:26               ` David Starks-Browning

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=NFBBLOMHALONCDMPGBLFAEBCCCAA.info@rlsystems.net \
    --to=info@rlsystems.net \
    --cc=cygwin@cygwin.com \
    --cc=starksb@ebi.ac.uk \
    /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).