From: Milan Crha <mcrha@redhat.com>
To: Rohan Garg <rohangarg@ubuntu.com>
Cc: Patrick Ohly <patrick.ohly@intel.com>,
Marcel Holtmann <marcel@holtmann.org>,
linux-bluetooth@vger.kernel.org, ying.an.deng@intel.com,
ulf.hofemeier@intel.com, ning.w.wang@intel.com,
Tino Keitel <tino.keitel+syncevolution@tikei.de>
Subject: Re: bluez 4.97: build failure when used in C++ apps
Date: Mon, 06 Feb 2012 09:46:13 +0100 [thread overview]
Message-ID: <1328517973.2036.8.camel@localhost> (raw)
In-Reply-To: <CAEb1ZdjiDFTngKg+zTMHgDQ7hNd6h+VAgbjeNJXQUyF+=d6a9Q@mail.gmail.com>
On Sun, 2012-02-05 at 16:29 +0530, Rohan Garg wrote:
> I can file a bug for tracking purposes and get the patched package in
> the archives, as long as upstream is willing to accept the patch ( or
> a modified version of the patch ) in the near future. I don't speak
> for the rest of the Ubuntu developers, but I consider the best
> approach to getting issues fixed in distros.
Hi,
I do not package bluez for Fedora, thus I've no idea about it, but we
found this issue while building on Fedora.
Rohan, is it a typo or you really meant to say "fixed in distro"? As far
as I can tell, all the major distros will suffer of the issue, thus why
should each of them apply patch on their own, when it belongs to
upstream, from my point of view?
Bye,
Milan
next prev parent reply other threads:[~2012-02-06 8:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:25 bluez 4.97: build failure when used in C++ apps Patrick Ohly
2012-01-16 8:48 ` Deng, Ying An
2012-01-16 9:24 ` Marcel Holtmann
2012-01-16 10:09 ` Patrick Ohly
2012-02-05 10:56 ` Patrick Ohly
2012-02-05 10:57 ` [PATCH] bluetooth.h: fix compile issue in C++ with ifdef Patrick Ohly
2012-02-05 11:07 ` Rohan Garg
2012-02-05 11:33 ` Patrick Ohly
2012-02-05 11:33 ` Rohan Garg
2012-02-05 12:23 ` Rohan Garg
2012-02-05 12:28 ` Rohan Garg
2012-02-05 10:59 ` bluez 4.97: build failure when used in C++ apps Rohan Garg
2012-02-05 12:02 ` Rohan Garg
2012-02-06 8:46 ` Milan Crha [this message]
2012-02-06 9:29 ` Patrick Ohly
2012-02-06 9:51 ` Milan Crha
2012-02-05 14:29 ` Tino Keitel
2012-02-05 14:50 ` Rohan Garg
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=1328517973.2036.8.camel@localhost \
--to=mcrha@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ning.w.wang@intel.com \
--cc=patrick.ohly@intel.com \
--cc=rohangarg@ubuntu.com \
--cc=tino.keitel+syncevolution@tikei.de \
--cc=ulf.hofemeier@intel.com \
--cc=ying.an.deng@intel.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;
as well as URLs for NNTP newsgroup(s).