Summary: | Convert libICE to ANSI C & related cleanup | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Peter Breitenlohner <peb> | ||||||||||||||||||||
Component: | Lib/ICE | Assignee: | Xorg Project Team <xorg-team> | ||||||||||||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||||||
Severity: | normal | ||||||||||||||||||||||
Priority: | medium | CC: | alan.coopersmith, pcpa | ||||||||||||||||||||
Version: | git | Keywords: | janitor, patch | ||||||||||||||||||||
Hardware: | All | ||||||||||||||||||||||
OS: | All | ||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||||||
Bug Depends on: | 18978 | ||||||||||||||||||||||
Bug Blocks: | |||||||||||||||||||||||
Attachments: |
|
Description
Peter Breitenlohner
2008-12-10 01:33:58 UTC
Created attachment 20993 [details] [review] patch 2/8 Created attachment 20994 [details] [review] patch 3/8 Created attachment 20995 [details] [review] patch 4/8 Created attachment 20996 [details] [review] patch 5/8 Created attachment 20997 [details] [review] patch 6/8 Created attachment 20998 [details] [review] patch 7/8 Created attachment 20999 [details] [review] patch 8/8 Using XORG_CWARNFLAGS from the util-macros-1.2.0 (release) fails for gcc-3.3.x and earlier. This has been fixed by recent util-macros git commits. Does this imply that a new release 1.2.1 is required and the first patch should require that newer version?? Created attachment 21230 [details] [review] patch 1/8 updated Hi Petter, Sorry for the delay. I just made the release of libICE 1.0.5 with all the patches applied. So far I think all patches you submited are of good quality, and correct. I think you should apply for an account in freedesktop, as apparently a "xorg janitors" list/group will not really be formed if things stay "as is" :-) |
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.