From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fwup: disable documentation build
Date: Tue, 21 Jun 2016 16:43:47 +0200 [thread overview]
Message-ID: <87twgmy53w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CA+-urNSj1yLeKcvY5Zpk5h+AfYP5J78k8k3crH_+ybk1=MQzWA@mail.gmail.com> (Frank Hunleth's message of "Tue, 21 Jun 2016 08:37:17 -0400")
>>>>> "Frank" == Frank Hunleth <fhunleth@troodon-software.com> writes:
> Hi Baruch,
> On Tue, Jun 21, 2016 at 8:16 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>> Documentation build with help2man relies on the output of running 'fwup
>> --help'. That obviously can't work with cross compilation.
> Fwiw, there was a nearly identical patch a while ago that hasn't been
> merged yet:
> http://patchwork.ozlabs.org/patch/634937/
> I prefer your commit comment, but I'm fine with whichever one gets
> merged first. So,
> Tested-by: Frank Hunleth <fhunleth@troodon-software.com>
Thanks. I've committed this and marked the earlier patch as superseeded.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2016-06-21 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 12:16 [Buildroot] [PATCH] fwup: disable documentation build Baruch Siach
2016-06-21 12:37 ` Frank Hunleth
2016-06-21 14:43 ` Peter Korsgaard [this message]
2016-06-21 14:41 ` Peter Korsgaard
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=87twgmy53w.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