From: Joseph Myers <joseph@codesourcery.com>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: <libc-alpha@sourceware.org>, Florian Weimer <fweimer@redhat.com>
Subject: Re: Remove add-ons mechanism
Date: Thu, 05 Oct 2017 21:30:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1710052129220.13964@digraph.polyomino.org.uk> (raw)
In-Reply-To: <2705773.B7uPsgh4F0@porto>
On Thu, 5 Oct 2017, Andreas K. Huettel wrote:
> Am Donnerstag, 5. Oktober 2017, 14:54:47 CEST schrieb Joseph Myers:
> > On Thu, 5 Oct 2017, Florian Weimer wrote:
> > > Their packaging is completely different from the libidn upstream releases.
> >
> > And updating from the libidn upstream releases would be problematic given
> > that it's a non-FSF-assigned project that has changed license.
>
> So what strategy is best to short-term fix bugs that have already been
> addressed by libidn upstream?
Well, you can, as always, apply changes from whatever source that are not
legally significant for copyright purposes.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-10-05 21:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 17:49 Joseph Myers
2017-09-28 22:01 ` Zack Weinberg
2017-09-28 22:38 ` Joseph Myers
2017-09-29 11:04 ` Florian Weimer
2017-09-30 6:35 ` Florian Weimer
2017-09-30 21:42 ` Joseph Myers
2017-10-05 10:39 ` Andreas K. Huettel
2017-10-05 11:07 ` Florian Weimer
2017-10-05 12:54 ` Joseph Myers
2017-10-05 13:16 ` libcidn (was: Re: Remove add-ons mechanism) Andreas K. Huettel
2017-10-05 13:39 ` libcidn Andreas Schwab
2017-10-05 13:40 ` libcidn Florian Weimer
2017-10-05 21:11 ` Remove add-ons mechanism Andreas K. Huettel
2017-10-05 21:30 ` Joseph Myers [this message]
2017-10-05 15:59 ` Joseph Myers
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=alpine.DEB.2.20.1710052129220.13964@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=dilfridge@gentoo.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).