From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Tim Waugh <twaugh@redhat.com>
Subject: Re: [Bluez-devel] CUPS backend fixes
Date: Thu, 06 Mar 2008 11:48:38 +0100 [thread overview]
Message-ID: <1204800518.13254.1.camel@californication> (raw)
In-Reply-To: <1204752334.2640.74.camel@cookie.hadess.net>
Hi Bastien,
> A few fixes, spotted by Tim Waugh.
>
> - Use CUPS error codes:
> https://bugzilla.redhat.com/show_bug.cgi?id=435082
> - Output STATE information (we still need to do that when we add retry
> support):
> https://bugzilla.redhat.com/show_bug.cgi?id=435083
> - Use DEVICE_URI envvar if available:
> https://bugzilla.redhat.com/show_bug.cgi?id=435080
> - Also add better error reporting from hcrp_print() and spp_print()
the patch has been applied. However I had to fix up the coding style and
actually fix an issue within the error handling in one of the loops. If
gcc gives you a warning about an uninitialized variable, please don't
ignore it. Most of the times there is something behind it.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-03-06 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 21:25 [Bluez-devel] CUPS backend fixes Bastien Nocera
2008-03-06 10:48 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-27 13:01 Bastien Nocera
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=1204800518.13254.1.camel@californication \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=twaugh@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox