From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] augeas: bump to version 1.9.0
Date: Mon, 15 Jan 2018 21:18:50 +0100 [thread overview]
Message-ID: <87fu76ub85.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180114163412.16548-1-joerg.krause@embedded.rocks> ("Jörg Krause"'s message of "Sun, 14 Jan 2018 17:34:12 +0100")
>>>>> "J?rg" == J?rg Krause <joerg.krause@embedded.rocks> writes:
> Add two patches from upstream to fix a build issue when building an
> example. Ideally, the examples should not be build at all. However,
> upstream disliked the idea of adding configure options like
> `--disable-examples` [1]. So we'll make do with the patches and force a
> autoreconf.
> Additionaly, the signature was checked and a hash for the license file
> is added.
> [1] https://github.com/hercules-team/augeas/issues/535
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> v2 (suggested by Thomas):
> * Add missing reference and SoB to upstream patches
> * Improve comment for AUTORECONF=YES
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-01-15 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 16:34 [Buildroot] [PATCH v2] augeas: bump to version 1.9.0 Jörg Krause
2018-01-15 20:18 ` Peter Korsgaard [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=87fu76ub85.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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