From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: [PATCH]
Date: Wed, 21 Dec 2005 15:11:18 +0100 [thread overview]
Message-ID: <1135174278.14627.3.camel@localhost> (raw)
In-Reply-To: <pan.2005.12.21.13.51.15.163756@esaurito.net>
Hi Filippo,
> > when D-Bus 1.0 has been released, I am going to drop support for older
> > versions anyway. However what you need to add is something like:
> >
> > #ifndef DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT
> > #define DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT 0x00
> > #endif
> >
> > This will work perfect instead of using your patch and is still backward
> > compatible.
>
> that's right! thank you, are you going to merge the above define into the
> next release of bluez?
it is already in the CVS. However I have some people doing the following
transition (instead of no flags):
DBUS_NAME_FLAG_PROHIBIT_REPLACEMENT -> DBUS_NAME_FLAG_DO_NOT_QUEUE
Any comments on this?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-21 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 13:54 [Bluez-devel] [PATCH] Filippo Giunchedi
2005-12-20 18:59 ` Marcel Holtmann
2005-12-21 13:51 ` [Bluez-devel] [PATCH] Filippo Giunchedi
2005-12-21 14:11 ` Marcel Holtmann [this message]
2005-12-21 15:28 ` [Bluez-devel] " Filippo Giunchedi
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=1135174278.14627.3.camel@localhost \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).