From: Mark Wielaard <mark@klomp.org>
To: Brett Gilio <brettg@gnu.org>
Cc: 38803@debbugs.gnu.org
Subject: [bug#38803] [PATCH] gnu: elfutils: Update to 0.178
Date: Mon, 30 Dec 2019 03:04:33 +0100 [thread overview]
Message-ID: <20191230020433.GA2695@wildebeest.org> (raw)
In-Reply-To: <aab04dc7-de8a-4214-b918-21749a921f7b@localhost>
Hi Brett,
On Mon, Dec 30, 2019 at 01:44:21AM +0000, Brett Gilio wrote:
> Funny you submitted this, I was working on the same package
> about an hour ago. We must be reading each other's minds. You got
> significantly farther than I did.
Thanks for looking at it. This is my first guix patch, so please be
gentle. I do maintain elfutils upstream, so I did have a little
advantage picking some upstream patches which hadn't gone into the
release yet.
> One thing I did do differently was that I extended the list of
> licenses to include the ones mentioned in the comment. I'll look at
> your patch, and hopefully this will be ready for core-updates. Thank
> you :)
Good you mention the licenses. I forgot to update them licenses. 0.178
introduces some new documentation (man pages), one of them is under
the GFDL (without invariant sections).
Also I am not sure how precisely we should mention the dual
gplv2+/lgplv3+ license for the "out" output libraries and the gplv3+
license for the "bin" output (and where the gfdl should be added).
Thanks,
Mark
next prev parent reply other threads:[~2019-12-30 2:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 1:41 [bug#38803] [PATCH] gnu: elfutils: Update to 0.178 Mark Wielaard
2019-12-30 1:44 ` Brett Gilio
2019-12-30 2:04 ` Mark Wielaard [this message]
2020-01-12 20:39 ` Mark Wielaard
2020-01-12 20:54 ` Marius Bakke
2020-01-13 0:03 ` Mark Wielaard
2020-01-13 22:26 ` Marius Bakke
2020-01-31 12:43 ` Mark Wielaard
2020-01-31 15:49 ` Marius Bakke
2020-01-31 16:55 ` Mark Wielaard
2020-02-05 20:41 ` Marius Bakke
2020-02-06 11:04 ` Mark Wielaard
2020-02-06 11:36 ` Marius Bakke
2020-02-06 13:23 ` Mark Wielaard
2020-02-06 14:31 ` Marius Bakke
2023-09-02 18:39 ` Vagrant Cascadian
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191230020433.GA2695@wildebeest.org \
--to=mark@klomp.org \
--cc=38803@debbugs.gnu.org \
--cc=brettg@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).