From: ludo@gnu.org (Ludovic Courtès)
To: Andy Patterson <ajpatter@uwaterloo.ca>
Cc: 25101-done@debbugs.gnu.org
Subject: bug#25101: [PATCH 1/2] gnu: Add hpaio-enabled sane-backends variant.
Date: Sat, 17 Dec 2016 23:12:41 +0100 [thread overview]
Message-ID: <87r356qk6e.fsf@gnu.org> (raw)
In-Reply-To: <20161214050325.6348-1-ajpatter@uwaterloo.ca> (Andy Patterson's message of "Wed, 14 Dec 2016 00:03:22 -0500")
Hello!
Andy Patterson <ajpatter@uwaterloo.ca> skribis:
> Here's some patches implementing what you've suggested. I decided to use the
> full "sane-backends" for the other dependents, since I guessed that they need
> some backend support. If anyone knows that that's not required, it can be
> changed.
I think that’s fine.
Applied all 3 patches. I also fixed a reproducibility issue due to
timestamps in a subsequent commit.
Thanks!
Ludo’.
next prev parent reply other threads:[~2016-12-17 22:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 18:41 bug#25101: simple-scan can't use hpaio Danny Milosavljevic
2016-12-04 4:00 ` Andy Patterson
2016-12-04 4:00 ` bug#25101: [PATCH 1/2] gnu: Add hpaio-enabled sane-backends variant Andy Patterson
2016-12-05 20:48 ` Ludovic Courtès
2016-12-05 22:38 ` Andy Patterson
2016-12-06 9:10 ` Ludovic Courtès
2016-12-12 20:11 ` Andy Patterson
2016-12-12 22:41 ` Ludovic Courtès
2016-12-14 5:03 ` Andy Patterson
2016-12-14 5:03 ` bug#25101: [PATCH 1/3] gnu: sane-backends: Disable backend generation Andy Patterson
2016-12-14 5:03 ` bug#25101: [PATCH 2/3] gnu: Add and use sane-backends-minimal Andy Patterson
2016-12-14 5:03 ` bug#25101: [PATCH 3/3] gnu: Add and use sane-backends Andy Patterson
2016-12-17 22:12 ` Ludovic Courtès [this message]
2016-12-04 4:00 ` bug#25101: [PATCH 2/2] gnu: simple-scan: Enable hpaio support Andy Patterson
2016-12-04 4:18 ` bug#25101: simple-scan can't use hpaio Andy Patterson
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r356qk6e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25101-done@debbugs.gnu.org \
--cc=ajpatter@uwaterloo.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).