From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Device specific configuration
Date: Wed, 04 Feb 2004 00:55:09 +0100 [thread overview]
Message-ID: <1075852509.13285.139.camel@pegasus> (raw)
In-Reply-To: <1075835938.2640.15.camel@akka.yeti.nocrew.org>
Hi Fredrik,
> > BTW did my patch work fine for you?
>
> Yes, I suppose you mainly changed indentation.
I also changed some other stuff, because I found it too complex. I need
some reports that this patch is working fine and not breaking the normal
expected behaviour.
> > What patch brings in "device default {..."? We don't need it, because we
> > can use "device {..." for it.
>
> It wasn't the same thing. "device { ... }" is the fallback device.
> "device default { ... }" was intended to set default parameters for all
> other device sections unless specified explicitly in those. But we can
> make that the same thing of course.
We need only one of them which is default and the <hciX> or <bdaddr> can
extend these default settings. Everything else is overload.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-02-03 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 16:52 [Bluez-devel] Device specific configuration Marcel Holtmann
2004-02-03 17:35 ` Fredrik Noring
2004-02-03 18:47 ` Marcel Holtmann
2004-02-03 19:18 ` Fredrik Noring
2004-02-03 23:55 ` 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=1075852509.13285.139.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=noring@nocrew.org \
/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