From: Daniele Benucci <d.benux@gmail.com>
To: Johan Hedberg <johan.hedberg@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Inconsistencies with UUIDs in XML service descriptors
Date: Mon, 12 Jan 2009 15:18:55 +0100 [thread overview]
Message-ID: <11f7a7550901120618r84faa0dwd1e1234bc3dfe63@mail.gmail.com> (raw)
In-Reply-To: <20090110124119.GA20941@localhost>
2009/1/10 Johan Hedberg <johan.hedberg@nokia.com>:
> Could you perhaps try to use git bisect
> to determine the exact patch that causes the bug?
According to git-bisect commit introducing the bug is
204180c7dc2e20b9b701275a3fefb52707720f54
(Make use of sdp_copy_record.)
Regards
Daniele.
--
Grabel's Law:
2 is not equal to 3 -- not even for large values of 2.
next prev parent reply other threads:[~2009-01-12 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11f7a7550901090850x4c276806v6c3c4bfad804986f@mail.gmail.com>
2009-01-09 16:52 ` Fwd: Inconsistencies with UUIDs in XML service descriptors Daniele Benucci
2009-01-10 12:02 ` Daniele Benucci
2009-01-10 12:41 ` Johan Hedberg
2009-01-12 14:18 ` Daniele Benucci [this message]
2009-01-12 14:32 ` Johan Hedberg
2009-01-12 20:47 ` Luiz Augusto von Dentz
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=11f7a7550901120618r84faa0dwd1e1234bc3dfe63@mail.gmail.com \
--to=d.benux@gmail.com \
--cc=johan.hedberg@nokia.com \
--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