From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libostree: disable manpages/documentation generation
Date: Sat, 2 Dec 2017 14:44:24 +0100 [thread overview]
Message-ID: <20171202144424.3f82a045@windsurf.lan> (raw)
In-Reply-To: <20171202075849.4439-1-marcus.folkesson@gmail.com>
Hello,
On Sat, 2 Dec 2017 08:58:49 +0100, Marcus Folkesson wrote:
> --enable-man is set to `auto` as default, which may break builds.
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> ---
> package/libostree/libostree.mk | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
Applied to master, thanks. I've added a reference to an autobuilder
failure that should be fixed by this. It would be good if you could add
such references yourself in the future when you submit a patch that
fixes a build failures.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-02 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 7:58 [Buildroot] [PATCH] libostree: disable manpages/documentation generation Marcus Folkesson
2017-12-02 13:44 ` Thomas Petazzoni [this message]
2017-12-02 13:59 ` Marcus Folkesson
2017-12-02 14:05 ` Thomas Petazzoni
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=20171202144424.3f82a045@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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