Summary: | stop Haze using deprecated things | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Simon McVittie <smcv> |
Component: | haze | Assignee: | Simon McVittie <smcv> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | jonny.lamb, xclaesse |
Version: | git master | Keywords: | patch |
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | review+ | ||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 31668 | ||
Attachments: |
[tp-glib master] Include channel-iface.h in telepathy-glib.h
[Haze master, 1/3] Use TP_ERRORS instead of deprecated TP_ERROR [Haze master, 2/3] Use non-deprecated TpIntset APIs [Haze master, 3/3] Use non-deprecated TpMessage APIs [Haze next] Use meta-headers and catch up with current 'next' branch |
Description
Simon McVittie
2012-05-07 10:25:40 UTC
Created attachment 61151 [details] [review] [tp-glib master] Include channel-iface.h in telepathy-glib.h On master, this was already included via channel-factory-iface.h; on next, that no longer works. Created attachment 61152 [details] [review] [Haze master, 1/3] Use TP_ERRORS instead of deprecated TP_ERROR Created attachment 61153 [details] [review] [Haze master, 2/3] Use non-deprecated TpIntset APIs Created attachment 61154 [details] [review] [Haze master, 3/3] Use non-deprecated TpMessage APIs --- Slight duplication of some things Jonny already did on next, but the merge is easy enough. Created attachment 61155 [details] [review] [Haze next] Use meta-headers and catch up with current 'next' branch --- Requires the telepathy-glib patch (Attachment #61151 [details]). Yes. Looks all good, +1 Thanks! (In reply to comment #1) > [tp-glib master] Include channel-iface.h in telepathy-glib.h Fixed for 0.19.0; (In reply to comment #2) > [Haze master, n/3] fixed for 0.7.0; (In reply to comment #5) > [Haze next] Use meta-headers and catch up with current 'next' branch fixed for ... a version. 1.0, I suppose. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.