From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] sane-backends: fix documentation build failure
Date: Sun, 09 Dec 2012 18:43:29 -0300 [thread overview]
Message-ID: <50C50601.3030306@zacarias.com.ar> (raw)
In-Reply-To: <87vccbvu3b.fsf@dell.be.48ers.dk>
On 12/09/2012 05:39 PM, Peter Korsgaard wrote:
> Did you have a look at moving to 1.0.23 instead?
Not really, i don't have a scanner handy for testing, so it would be
just a blind build test.
Also it's unlikely it would have fixed the documentation issue.
Regards.
next prev parent reply other threads:[~2012-12-09 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 14:35 [Buildroot] [PATCH] sane-backends: fix documentation build failure Gustavo Zacarias
2012-12-09 20:39 ` Peter Korsgaard
2012-12-09 21:43 ` Gustavo Zacarias [this message]
2012-12-09 20:59 ` 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=50C50601.3030306@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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 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.