From: Marius Bakke <mbakke@fastmail.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Brett Gilio <brettg@gnu.org>, 38803@debbugs.gnu.org
Subject: [bug#38803] [PATCH] gnu: elfutils: Update to 0.178
Date: Wed, 05 Feb 2020 21:41:50 +0100 [thread overview]
Message-ID: <87d0as6a29.fsf@devup.no> (raw)
In-Reply-To: <20200131165505.GN3319@wildebeest.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Mark Wielaard <mark@klomp.org> writes:
> OK, OK. Lets see if I can at least get the patch that does only update
> the descriptions correct. New version attached.
Thanks! I fixed the comment typo and committed. The new description
should show up on <https://guix.gnu.org/packages/E/page/3/> shortly. :-)
Note that I had to convert the patch from ISO-8859-14 to UTF-8 in order
to make git accept it:
$ iconv -f ISO-8859-14 -t UTF-8 0001-gnu-elfutils-Update-synopsis-and-description.patch | git am -s
Not sure what happened, perhaps it got mangled by your MUA?
For the 0.178 update, perhaps we can add the new version as a separate
variable until we figure out how to isolate libelf.so? That can be done
on the 'master' branch as long as we don't change the current 'elfutils'
package.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-05 20:43 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0as6a29.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=38803@debbugs.gnu.org \
--cc=brettg@gnu.org \
--cc=mark@klomp.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.