public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Aaron Merey <amerey@redhat.com>
To: Simon Marchi <simark@simark.ca>
Cc: binutils@sourceware.org, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] config/debuginfod.m4: Rewrite with pkg-config
Date: Wed, 04 Mar 2020 19:31:00 -0000	[thread overview]
Message-ID: <CAJDtP-R2g1kKSpfYQ5PdFsaqF+qx0Z6t04WQDM=n+3k9t5_SbA@mail.gmail.com> (raw)
In-Reply-To: <0eb3d2e4-16f9-4151-81aa-4f80a208c015@simark.ca>

On Wed, Mar 4, 2020 at 2:24 PM Simon Marchi <simark@simark.ca> wrote:
> I don't really see the problem, we do distribute software for which the FSF doesn't
> hold the copyright, like zlib.  As long as we don't pretend that it's FSF-owned code,
> what's the problem?  And the GPLv2+ license means it's GLPv3-compatible.

This issue was originally flagged by Tom, maybe he can speak to it further.

Aaron

      reply	other threads:[~2020-03-04 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  0:15 Aaron Merey
2020-03-04  2:33 ` Simon Marchi
2020-03-04 19:20   ` Aaron Merey
2020-03-04 19:24     ` Simon Marchi
2020-03-04 19:31       ` Aaron Merey [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='CAJDtP-R2g1kKSpfYQ5PdFsaqF+qx0Z6t04WQDM=n+3k9t5_SbA@mail.gmail.com' \
    --to=amerey@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=simark@simark.ca \
    --cc=tom@tromey.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).