From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: pacho@condmat1.ciencias.uniovi.es
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez-hcidump-1.42 fails to build against bluez-4.61
Date: Mon, 8 Mar 2010 15:05:18 +0100 [thread overview]
Message-ID: <20100308150518.7f5b79a5@strolchi> (raw)
In-Reply-To: <1268056614.7822.4.camel@localhost.localdomain>
On Mon, 08 Mar 2010 14:56:54 +0100
Pacho Ramos <pacho@condmat1.ciencias.uniovi.es> wrote:
> We should then simply wait for bluez-4.62 and, then, no patches would be
> needed for bluez-hcidump, not? (or I have missed anything?)
Yes, I verified this already: after I had updated bluez to 4.62 in the
openSUSE buildservice, I could safely drop the two patches from the
bluez-hcidump package and it still builds fine.
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
next prev parent reply other threads:[~2010-03-08 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 18:48 bluez-hcidump-1.42 fails to build against bluez-4.61 Pacho Ramos
2010-03-05 19:30 ` Stefan Seyfried
2010-03-07 21:43 ` Marcel Holtmann
2010-03-08 13:56 ` Pacho Ramos
2010-03-08 14:05 ` Stefan Seyfried [this message]
2010-03-08 14:36 ` Pacho Ramos
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=20100308150518.7f5b79a5@strolchi \
--to=stefan.seyfried@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pacho@condmat1.ciencias.uniovi.es \
/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