From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Bluetooth 2.6.12-2.6.13 Patch
Date: Mon, 29 May 2006 15:09:02 +0200 [thread overview]
Message-ID: <1148908142.31689.21.camel@localhost> (raw)
In-Reply-To: <65d9a561.be867fa1.8220b00@expms5.cites.uiuc.edu>
Hi Mark,
> Okay, so that was a dumb question - there were two lines
> difference.
>
> Can anyone give me a bit more info as to what bug those were
> trying to fix?
be more specific, because I have no idea what you are talking about.
Regards
Marcel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-05-29 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 15:35 [Bluez-devel] Bluetooth 2.6.12-2.6.13 Patch Mark Murphy
2006-05-29 13:09 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-25 21:36 Mark Murphy
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=1148908142.31689.21.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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