bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>,
	 "Daniel Richard G." <skunk@iskunk.org>
Subject: Re: nan: Relicense under LGPLv2+
Date: Thu, 18 Apr 2024 15:17:28 -0500	[thread overview]
Message-ID: <7r52if7mfwres3w7qppyino66ncv5xijeagrvt6yhzu5jjxpqr@2zcqgj6m4vsv> (raw)
In-Reply-To: <11109859.Pb81n1uba9@nimes>

On Thu, Apr 18, 2024 at 01:09:19AM +0200, Bruno Haible wrote:
> The module 'nan' (previously tests/nan.h, now lib/nan.h) defines functions
> for getting a NaN value reliably. This module is, so far, under GPL,
> because historically only the tests use it.
> 
> I would like to use it under LGPLv2+, for the modules 'setpayload*'
> and 'getpayloadl' (functions defined by ISO C 23 and implemented in glibc).
> 
> Can I have your agreement to relicensing your contributions to this
> module under LGPLv2+, please?
> 
>   * Eric Blake:
>     https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=ecab4471c7da5d367a62c8db75ee54ed6d948e40#patch11

Yes, I have no problems with my contributions being LGPLv2+ on this
module.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.
Virtualization:  qemu.org | libguestfs.org



  reply	other threads:[~2024-04-18 20:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17 23:09 nan: Relicense under LGPLv2+ Bruno Haible
2024-04-18 20:17 ` Eric Blake [this message]
2024-04-20 20:53 ` Paul Eggert
2024-04-21  0:16   ` Bruno Haible

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=7r52if7mfwres3w7qppyino66ncv5xijeagrvt6yhzu5jjxpqr@2zcqgj6m4vsv \
    --to=eblake@redhat.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=skunk@iskunk.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).