public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Hiroaki.Fuse@sony.com
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	"libc-stable@sourceware.org" <libc-stable@sourceware.org>
Subject: Re: [PATCH] nscd: Move declarations used in the library out of <nscd.h>
Date: Thu, 13 Jul 2023 10:27:36 +0200	[thread overview]
Message-ID: <87351s1aiv.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <TYCPR01MB6963FE1B3FEA5A6D7A90BD6DEA37A@TYCPR01MB6963.jpnprd01.prod.outlook.com> (Hiroaki's message of "Thu, 13 Jul 2023 08:06:11 +0000")

* Hiroaki:

> Dear Florian Weimer,
>
> Thank you for your quick update.
> My understanding is that we can conclude the license of glibc as LGPLv2.1
> after applying your patch. Is it correct?

You need to perform your own license analysis.  There are some resources
that could help you, like the LICENSES file in the source tree.  I'm not
sure everyone would agree that “LGPLv2.1” is an accurate summary.

Thanks,
Florian


      reply	other threads:[~2023-07-13  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 12:43 Florian Weimer
2023-07-13  8:06 ` Hiroaki.Fuse
2023-07-13  8:27   ` Florian Weimer [this message]

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=87351s1aiv.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=Hiroaki.Fuse@sony.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-stable@sourceware.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).