From: Bastien Nocera <hadess@hadess.net>
To: dev-zero@gentoo.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Use cups-config instead of hardcoded location
Date: Tue, 07 Apr 2009 11:25:48 +0100 [thread overview]
Message-ID: <1239099948.20817.15.camel@cookie.hadess.net> (raw)
In-Reply-To: <1239094799.19235.2.camel@localhost>
On Tue, 2009-04-07 at 10:59 +0200, Tiziano Müller wrote:
> Hi there
>
> This patch has been sitting in our cvs repo for ages:
> Use cups-config instead of hardcoded cups-location.
This check should be done in configure.ac, along with a default if
cups-config isn't available. Otherwise we'll end up with stuff
in /backend and warnings during the build.
prev parent reply other threads:[~2009-04-07 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 8:59 [PATCH] Use cups-config instead of hardcoded location Tiziano Müller
2009-04-07 10:25 ` Bastien Nocera [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=1239099948.20817.15.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=dev-zero@gentoo.org \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox