public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: Stefan Seyfried <stefan.seyfried@googlemail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluez-hcidump-1.42 fails to build against bluez-4.61
Date: Mon, 08 Mar 2010 15:36:14 +0100	[thread overview]
Message-ID: <1268058974.7822.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20100308150518.7f5b79a5@strolchi>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

El lun, 08-03-2010 a las 15:05 +0100, Stefan Seyfried escribió:
> 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.

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

Thanks a lot

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-03-08 14:36 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
2010-03-08 14:36         ` Pacho Ramos [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=1268058974.7822.6.camel@localhost.localdomain \
    --to=pacho@condmat1.ciencias.uniovi.es \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stefan.seyfried@googlemail.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