From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] 2 more patches for bluez-gnome
Date: Tue, 24 Jul 2007 17:23:33 +0100 [thread overview]
Message-ID: <1185294213.3641.136.camel@cookie.hadess.net> (raw)
In-Reply-To: <1185291723.7111.58.camel@violet>
On Tue, 2007-07-24 at 17:42 +0200, Marcel Holtmann wrote:
> 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.
What other way do you think we should check for the availability of
nautilus and the obexftp gnome-vfs module?
It's quite ugly, but it mimicks what gnome-vfs does, without using
gnome-vfs directly. I could move it to a different helper file if that's
any help.
--
Bastien Nocera <hadess@hadess.net>
-------------------------------------------------------------------------
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 16:23 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
2007-07-24 16:23 ` Bastien Nocera [this message]
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=1185294213.3641.136.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--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