Return-Path: <cyrus@holtmann.org>
Subject: Re: bluez-hcidump-1.42 fails to build against bluez-4.61
From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
Reply-To: pacho@condmat1.ciencias.uniovi.es
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org
In-Reply-To: <20100308150518.7f5b79a5@strolchi>
References: <20100308150518.7f5b79a5@strolchi>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-YfMH8AGH3jPUgWSluExc"
Date: Mon, 08 Mar 2010 15:36:14 +0100
Message-Id: <1268058974.7822.6.camel@localhost.localdomain>
Mime-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>


--=-YfMH8AGH3jPUgWSluExc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

El lun, 08-03-2010 a las 15:05 +0100, Stefan Seyfried escribi=C3=B3:
> On Mon, 08 Mar 2010 14:56:54 +0100
> Pacho Ramos <pacho@condmat1.ciencias.uniovi.es> wrote:
>=20
> > We should then simply wait for bluez-4.62 and, then, no patches would b=
e
> > needed for bluez-hcidump, not? (or I have missed anything?)
>=20
> 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.

Yes, I have just confirmed it, sorry for the inconvenience, I didn't
notice 4.62 was already released

Thanks a lot

--=-YfMH8AGH3jPUgWSluExc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
 digitalmente

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEABECAAYFAkuVC14ACgkQCaWpQKGI+9T7XwCfTFX+1qD0BfM+elT9s/qw6dNN
LVUAnA/AJ2zohz2fRW8/3EtBJn98bUdJ
=HxyY
-----END PGP SIGNATURE-----

--=-YfMH8AGH3jPUgWSluExc--