Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Add conf file support
Date: Wed, 25 May 2011 12:48:02 -0700	[thread overview]
Message-ID: <1306352882.2681.43.camel@aeonflux> (raw)
In-Reply-To: <BANLkTikKXPx-FgPB5nR6H9LKVTHGdLaggQ@mail.gmail.com>

Hi Luiz,

> >> This should reduce the amount of options which normally don't change
> >> each time obexd is executed.
> >> ---
> >>  Makefile.am   |    2 +-
> >>  plugins/ftp.c |    8 ++-
> >>  src/main.c    |  173 +++++++++++++++++++++++++++++++++++++++-----------------
> >>  3 files changed, 127 insertions(+), 56 deletions(-)
> >
> > I do not want to have config file support for obexd.
> >
> 
> Alright, then I will just update the documentation of the current
> options to be more detailed and remove the old configuration file that
> still exists on the repository.

I don't know how much Johan mentioned on IRC, but what we should be
doing is by default enable all compiled in plugins and then use -p and
-P command line switches to control what gets enabled and what not. And
that can be done easily in the D-Bus autostart file.

Regards

Marcel



  reply	other threads:[~2011-05-25 19:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 16:12 [PATCH 1/2] Add conf file support Luiz Augusto von Dentz
2011-05-24 16:12 ` [PATCH 2/2] Simplify options for including/excluding plugins Luiz Augusto von Dentz
2011-05-25  0:39 ` [PATCH 1/2] Add conf file support Marcel Holtmann
2011-05-25  6:14   ` Luiz Augusto von Dentz
2011-05-25 19:48     ` Marcel Holtmann [this message]
2011-05-25 19:58       ` Luiz Augusto von Dentz
  -- strict thread matches above, loose matches on Subject: below --
2011-05-17  8:17 Luiz Augusto von Dentz
2011-05-20 18:04 ` Johan Hedberg
2011-05-20 18:37   ` Marcel Holtmann
2011-05-20 19:17     ` Luiz Augusto von Dentz

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=1306352882.2681.43.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox