From: Marcel Holtmann <marcel@holtmann.org>
To: Brian Gix <bgix@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: -DG_DISABLE_DEPRECATED and g_io_channel_*()
Date: Wed, 19 Jan 2011 12:25:12 +0100 [thread overview]
Message-ID: <1295436312.3873.240.camel@aeonflux> (raw)
In-Reply-To: <1295377703.1774.6.camel@ubuntuLab1>
Hi Brian,
> There appears to be a number of deprecated g_io_channel_* functions
> being called from the bluez tip, which are breaking the build due to
> Marcel's latest commit today:
>
> commit effe770cd43cf53fa5842291941dbfc82beab645
> Author: Marcel Holtmann <marcel@holtmann.org>
> Date: Tue Jan 18 14:56:31 2011 +0100
>
> Use -DG_DISABLE_DEPRECATED compiler define
>
>
> Should this commit be backed out until these deprecated usages have been
> fixed, or is this the general way that the issue is forced?
>
> Obviously deprecated functions should not be used, but it creates an
> unbuildable bluez in the meantime.
I broke it on purpose to draw some attention to this ;)
Regards
Marcel
next prev parent reply other threads:[~2011-01-19 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 19:08 -DG_DISABLE_DEPRECATED and g_io_channel_*() Brian Gix
2011-01-19 11:25 ` Marcel Holtmann [this message]
2011-01-19 12: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=1295436312.3873.240.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=bgix@codeaurora.org \
--cc=linux-bluetooth@vger.kernel.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