All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Alexander Orlenko <zxteam@gmail.com>
Cc: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>,
	Bastien Nocera <hadess@hadess.net>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [GSoC'10] : New Command Line Tool(s) for bluez
Date: Tue, 17 Aug 2010 00:59:21 -0300	[thread overview]
Message-ID: <20100817035921.GA5900@vigoh> (raw)
In-Reply-To: <AANLkTimW1SmfZ+j=F7kTSwosdz=kh+g9ofcqdTeGE7CB@mail.gmail.com>

Hi Alexander,

* Alexander Orlenko <zxteam@gmail.com> [2010-08-16 10:24:23 +1100]:

> Hi everyone,
> 
> I updated project info page at http://hostisdown.org/gsoc/projects/bluez-tools
> Created project home page: http://code.google.com/p/bluez-tools
> Current release available for download: 0.1.18-6432
> 
> Code of my project does not based on non-GTK parts of
> libgnome-bluetooth. I wrote glib gobjects for all bluez dbus
> interfaces.
> I will continue developing my project after end of GSoC.

Why have you decided to write a binary for each functionality? What do
you think about have them all in only one binary? (or at least the
bluetoothd related ones)


-- 
Gustavo F. Padovan
http://padovan.org

  parent reply	other threads:[~2010-08-17  3:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 13:04 [GSoC'10] : New Command Line Tool(s) for bluez Alexander Orlenko
2010-05-20 13:08 ` Bastien Nocera
2010-05-21  7:29   ` Andrei Emeltchenko
2010-08-15 23:24     ` Alexander Orlenko
2010-08-16  9:40       ` Bastien Nocera
2010-08-16 12:06         ` Alexander Orlenko
2010-08-16 13:35           ` alok barsode
2010-08-17  3:27         ` Gustavo F. Padovan
2010-08-17  3:59       ` Gustavo F. Padovan [this message]
2010-08-17  4:55         ` Alexander Orlenko
2010-08-17  8:16           ` alok barsode

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=20100817035921.GA5900@vigoh \
    --to=gustavo@padovan.org \
    --cc=andrei.emeltchenko.news@gmail.com \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zxteam@gmail.com \
    /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.