From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2 more patches for bluez-gnome
Date: Tue, 24 Jul 2007 17:42:03 +0200 [thread overview]
Message-ID: <1185291723.7111.58.camel@violet> (raw)
In-Reply-To: <1185233353.3641.82.camel@cookie.hadess.net>
Hi Bastien,
> The descriptions of each patch are in the patches, thanks git.
most of your patches are in the CVS now. I dropped the thread stuff and
removed the obexftp check since that is too ugly. Need to do some
autoconf/automake magic first.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-24 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 23:29 [Bluez-devel] 2 more patches for bluez-gnome Bastien Nocera
2007-07-24 15:42 ` Marcel Holtmann [this message]
2007-07-24 16:23 ` Bastien Nocera
2007-07-24 16:25 ` [Bluez-devel] Bluetooth 2.1 Spec TJ OConnor
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=1185291723.7111.58.camel@violet \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.