All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [BlueZ-Announce] Release	of	bluez-libs-3.26	and	bluez-utils-3.26
Date: Mon, 11 Feb 2008 03:33:17 +0100	[thread overview]
Message-ID: <1202697197.7664.144.camel@violet> (raw)
In-Reply-To: <1202694454.3491.129.camel@cookie.hadess.net>

Hi Bastien,

> > And I am thinking about simply adding the support for FTP to bluez-gnome
> > since the dependencies of gnome-user-share are a little bit too much.
> 
> The same as bluez-gnome plus httpd and avahi. Could you add a way to
> disable the bluez-gnome code? I'm thinking of adding obexpush support in
> gnome-user-share as well, as it's the better place to have it, thinking
> desktop-wide.

I have OPP and FTP support in bluez-gnome now. Was actually pretty
simple. The only problem is that we can't reject requests and that no
pairing is triggered.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-02-11  2:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1202692346.7664.129.camel@violet>
2008-02-11  1:23 ` [Bluez-devel] [BlueZ-Announce] Release of bluez-libs-3.26 and bluez-utils-3.26 Bastien Nocera
2008-02-11  1:31   ` Marcel Holtmann
2008-02-11  1:47     ` Bastien Nocera
2008-02-11  2:33       ` Marcel Holtmann [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=1202697197.7664.144.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.