From: Tim Waugh <twaugh@redhat.com>
To: Till Kamppeter <till.kamppeter@gmail.com>,
Debian-printing@lists.debian.org,
Open Printing <printing-architecture@lists.linux-foundation.org>
Subject: Re: [Printing-architecture] Upstream future of ippusbxd
Date: Tue, 07 Jul 2015 16:33:44 +0100 [thread overview]
Message-ID: <1436283224.3308.2.camel@redhat.com> (raw)
In-Reply-To: <559B2849.7060907@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
On Mon, 2015-07-06 at 22:15 -0300, Till Kamppeter wrote:
> I am thinking about joining it into the cups-filters upstream package
> to not have too many tiny packages to make up the complete printing
> stack and cups-filters contains all manufacturer-independent software
> for communication with printers which is not part of CUPS itself.
I don't really have a strong opinion either way. Having it in its own
package would be fine for me, but if you want to put it in cups-filters
I'd be OK with that too.
What I would definitely prefer is to have it hosted in git not bzr. :-)
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-07 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 1:15 [Printing-architecture] Upstream future of ippusbxd Till Kamppeter
2015-07-07 8:47 ` Johannes Meixner
2015-07-07 12:10 ` James Cloos
2015-07-07 14:16 ` Johannes Meixner
2015-07-07 16:02 ` James Cloos
2015-07-08 9:12 ` Johannes Meixner
2015-07-08 12:40 ` Ira McDonald
2015-07-08 14:10 ` Tim Waugh
2015-07-08 18:59 ` Till Kamppeter
2015-07-13 10:05 ` Tim Waugh
2015-07-07 15:33 ` Tim Waugh [this message]
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=1436283224.3308.2.camel@redhat.com \
--to=twaugh@redhat.com \
--cc=Debian-printing@lists.debian.org \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=till.kamppeter@gmail.com \
/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.