From: Eric Blake <ebb9@byu.net>
To: cygwin-apps@cygwin.com, cygwin-licensing@cygwin.com
Subject: Re: GPLv3
Date: Sun, 01 Jul 2007 14:24:00 -0000 [thread overview]
Message-ID: <4687B921.3040209@byu.net> (raw)
In-Reply-To: <4687B75A.9020700@byu.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Eric Blake on 7/1/2007 8:16 AM:
> Thanks for the reminder about the exception clause. Since packaging tar
> 1.18 does not modify the sources to cygwin1.dll, I agree that the GPLv2
> exception offered by cygwin is applicable here. I don't think GPLv3 will
> have any problem achieving OSI exemption, so I went ahead and uploaded tar
^^^^^^^^^
s/exemption/certification/
> 1.18.
>
- --
Don't work too hard, make some time for fun as well!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGh7kh84KuGfSFAYARAoY3AJ9db/zOanxXJVrBW+bNVK3g89JAqACfUnvA
aI97GzUEhVFdtSamiWA27AE=
=70HC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-07-01 14:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 3:46 GPLv3 Eric Blake
2007-07-01 4:12 ` GPLv3 Brian Dessent
2007-07-01 14:17 ` GPLv3 Eric Blake
2007-07-01 14:24 ` Eric Blake [this message]
2007-07-02 7:40 ` GPLv3 Corinna Vinschen
2007-07-02 14:40 ` GPLv3 Andrew Schulman
2007-07-02 15:18 ` GPLv3 Corinna Vinschen
2007-07-02 15:29 ` GPLv3 Andrew Schulman
2007-07-02 18:04 ` GPLv3 Corinna Vinschen
2007-07-02 20:09 ` GPLv3 Yaakov (Cygwin Ports)
2007-07-02 23:29 ` GPLv3 Dave Korn
2007-07-02 23:52 ` GPLv3 Yaakov (Cygwin Ports)
2007-07-03 7:09 ` GPLv3 Corinna Vinschen
2007-07-03 17:45 ` GPLv3 Dave Korn
2007-07-03 18:07 ` GPLv3 Corinna Vinschen
2007-07-02 20:15 ` GPLv3 Yaakov (Cygwin Ports)
2007-07-05 2:33 ` GPLv3 Eric Blake
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=4687B921.3040209@byu.net \
--to=ebb9@byu.net \
--cc=cygwin-apps@cygwin.com \
--cc=cygwin-licensing@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).