It might be nice to put together a wiki page with pointers to the
various patches that are needed for CK support in 3.16
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
On Wed, 2015-02-04 at 10:24 +0100, Olav Vitters wrote:
On Tue, Feb 03, 2015 at 03:36:36PM -0500, Ray Strode wrote:
Hi,
On Tue, Feb 3, 2015 at 12:00 PM, Olav Vitters o...@vitters.nl wrote:
Can't we hide it behind a --this-is-going-away-in-3.18 configure switch?
That was certainly a
On Tue, Feb 03, 2015 at 03:36:36PM -0500, Ray Strode wrote:
Hi,
On Tue, Feb 3, 2015 at 12:00 PM, Olav Vitters o...@vitters.nl wrote:
Can't we hide it behind a --this-is-going-away-in-3.18 configure switch?
That was certainly a possibility, but, what's the advantage of doing
it? The bug
tl;dr Might happen soon.
While/after upgrading to Bugzilla 4.4 soon(TM) [1], I would like to get
rid of Bugzilla's trivial Severity field value in order to get a
slightly shorter list of confusing choices.
That means it will not be possible anymore to set that Severity value on
a bug report,
On Tue, 03.02.15 18:29, Cosimo Cecchi (cosi...@gnome.org) wrote:
On Mon, Feb 2, 2015 at 3:22 AM, Lennart Poettering mzta...@0pointer.de
wrote:
Oh no, that's not what I meant. I was more proposing to pull them
once, while you develop your stuff, and then shipping them in your own
Hi,
On Wed, Feb 4, 2015 at 4:24 AM, Olav Vitters o...@vitters.nl wrote:
Having a configure option would not
mean it is suddenly gone (if they miss this email, they'd also not know
about the patch), but it clearly tells them it'll be gone.
Okay so there's a pretty good middle ground we can
On Wed, Feb 04, 2015 at 09:48:19AM -0500, Ray Strode wrote:
On Wed, Feb 4, 2015 at 4:24 AM, Olav Vitters o...@vitters.nl wrote:
Having a configure option would not
mean it is suddenly gone (if they miss this email, they'd also not know
about the patch), but it clearly tells them it'll be
