From: Karl Berry <karl@freefriends.org>
To: bug-gnulib@gnu.org
Subject: Re: Relicensing policy & weak copyleft
Date: Thu, 19 Sep 2013 15:52:33 -0600 [thread overview]
Message-ID: <86y56swkbi.fsf@frenzy.freefriends.org> (raw)
In-Reply-To: <523B70F4.3020301@cs.ucla.edu> (message from Paul Eggert on Thu, 19 Sep 2013 14:47:32 -0700)
The difference lies in *non*-glibc functionality offered by gnulib.
Of which there is also plenty, afaik.
k
next prev parent reply other threads:[~2013-09-19 21:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 17:51 Request to relicense hash gnulib module to LGPLv2+ Richard W.M. Jones
2013-09-09 8:11 ` Richard W.M. Jones
2013-09-12 15:33 ` Eric Blake
2013-09-12 15:36 ` Simon Josefsson
2013-09-12 16:51 ` Paul Eggert
2013-09-12 17:05 ` Eric Blake
2013-09-12 17:39 ` Paul Eggert
2013-09-19 12:23 ` Relicensing policy & weak copyleft Ludovic Courtès
2013-09-19 15:17 ` Paul Eggert
2013-09-19 21:40 ` Karl Berry
2013-09-19 21:47 ` Paul Eggert
2013-09-19 21:52 ` Karl Berry [this message]
2013-09-19 22:44 ` Paul Eggert
2013-09-23 9:31 ` Richard W.M. Jones
2013-09-23 15:35 ` Ludovic Courtès
2020-02-22 17:33 ` Bruno Haible
2013-11-05 15:51 ` Request to relicense hash gnulib module to LGPLv2+ Richard W.M. Jones
2013-11-05 16:29 ` Jim Meyering
2013-11-05 16:53 ` Richard W.M. Jones
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86y56swkbi.fsf@frenzy.freefriends.org \
--to=karl@freefriends.org \
--cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).