From: Michael Sweet <msweet@apple.com>
To: "Gutenprint (formerly Gimp-Print) printer driver development"
<gimp-print-devel@lists.sourceforge.net>
Cc: "printing-architecture@lists.linux-foundation.org"
<printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] [Gimp-print-devel] RFC: Patch for (libusb-based) USB backend for quirks files
Date: Mon, 05 Aug 2013 10:48:41 -0400 [thread overview]
Message-ID: <3E79CFAC-56AE-4941-A48E-EBE1BBA2E871@apple.com> (raw)
In-Reply-To: <20130803011708.GA4773@shaftnet.org>
Sorry, too much happening at the moment and I forgot that the USB quirks stuff is part of 1.6.4, not 1.6.3. 1.6.4 will be coming out "soon".
On 2013-08-02, at 9:17 PM, Solomon Peachy <pizza@shaftnet.org> wrote:
> On Thu, Aug 01, 2013 at 10:57:36AM -0400, Michael Sweet wrote:
>> The necessary changes are part of CUPS 1.6.3 and 1.7rc1 that were
>> released on the 11th.
>
> Either I am being more special than usual, or the necessary changes
> didn't make it into either of those releases. Neither none seems to
> have support for an external usb quirks file, unless the committed code
> is radically different from the patch you posted here.
>
> - Solomon
> --
> Solomon Peachy pizza at shaftnet dot org
> Delray Beach, FL ^^ (email/xmpp) ^^
> Quidquid latine dictum sit, altum viditur.
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk_______________________________________________
> Gimp-print-devel mailing list
> Gimp-print-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
next prev parent reply other threads:[~2013-08-05 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 16:02 [Printing-architecture] RFC: Patch for (libusb-based) USB backend for quirks files Michael Sweet
2013-07-18 17:51 ` Till Kamppeter
2013-07-18 19:05 ` Michael Sweet
2013-07-18 21:06 ` Till Kamppeter
2013-07-18 23:44 ` Michael Sweet
[not found] ` <20130801145448.GA10904@shaftnet.org>
2013-08-01 14:57 ` [Printing-architecture] [Gimp-print-devel] " Michael Sweet
[not found] ` <20130803011708.GA4773@shaftnet.org>
2013-08-05 14:48 ` Michael Sweet [this message]
[not found] <m3a9lku1ia.fsf@dsl092-065-009.bos1.dsl.speakeasy.net>
2013-07-18 2:28 ` Michael Sweet
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=3E79CFAC-56AE-4941-A48E-EBE1BBA2E871@apple.com \
--to=msweet@apple.com \
--cc=gimp-print-devel@lists.sourceforge.net \
--cc=printing-architecture@lists.linux-foundation.org \
/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.