From: Peter Robinson <pbrobinson@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] HCID D-Bus
Date: Fri, 9 Sep 2005 09:25:16 +0100 [thread overview]
Message-ID: <5256d0b050909012577fcb19c@mail.gmail.com> (raw)
In-Reply-To: <1126220839.5286.57.camel@blade>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
>
> > 1. Develop a common code addressing all D-Bus versions
>
> not needed, because my plan is to drop support for anything below D-Bus
> version 0.5 (which should be compatible with D-Bus 0.3x) starting with
> bluez-utils-0.22. My original plan was to do it in next release, but
> there are some memory leak fixes and I want to get out a new version as
> soon as possible. However maybe it is a good idea to drop support for
> older D-Bus versions now.
I think 0.5 is compatible with >0.35. The current FC4 only uses 0.33 and I
don't think its compatible with >0.35. I think this is similar for a number
of the current releases (I think most with gnome 2.10) but obviously isn't
the case for the development streams that aren't releases yet.
Pete
[-- Attachment #2: Type: text/html, Size: 963 bytes --]
next prev parent reply other threads:[~2005-09-09 8:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 19:50 [Bluez-devel] HCID D-Bus Claudio Takahasi
2005-09-08 23:07 ` Marcel Holtmann
2005-09-09 8:25 ` Peter Robinson [this message]
2005-09-09 9:37 ` Marcel Holtmann
2005-09-09 13:29 ` Sjoerd Simons
2005-09-09 13:40 ` Marcel Holtmann
2005-09-12 21:07 ` [Bluez-devel] HCID D-Bus (Sig Fault) Claudio Takahasi
2005-09-12 21:14 ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-12 21:40 ` [Bluez-devel] HCID D-Bus (Sig Fault) Marcel Holtmann
2005-09-12 23:09 ` Claudio Takahasi
2005-09-12 23:21 ` Marcel Holtmann
2005-09-13 13:03 ` [Bluez-devel] HCID D-Bus (Seg Fault) Claudio Takahasi
2005-09-13 18:54 ` Marcel Holtmann
2005-09-14 12:00 ` Claudio Takahasi
2005-09-14 15:16 ` Marcel Holtmann
2005-09-14 16:06 ` Claudio Takahasi
2005-09-15 8:11 ` Marcel Holtmann
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=5256d0b050909012577fcb19c@mail.gmail.com \
--to=pbrobinson@gmail.com \
--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.