Re: gtk-devel-list Digest, Vol 157, Issue 16

[Daniel Boles <dboles src gmail com>]

I can't speak for any maintainers, but I suspect that constantly pinging like this does not have any significant - or at least significant positive -  effect on the chance of the tickets being bumped forward in the queue. I believe that pinging is generally discouraged, especially when you do it across channels like this, i.e. not at least confining the pinging to Bugzilla.

Remember that contributors have many other things they are working on, and those who happen to see these messages may not have specific enough knowledge to make a decision one way or another. Also, all of this is done completely for free, so there's that too.

On 25 May 2017 at 13:00, <gtk-devel-list-request gnome org> wrote:

Today's Topics:

   1. Re: gdk-pixbuf: Add IANA registered image/emf and image/wmf
      (Ingo Br?ckl)
   2. Re: Bug 554926 still in 2.24.31 (Ingo Br?ckl)


----------------------------------------------------------------------

Message: 1
Date: Thu, 25 May 2017 10:47:50 +0200
From: Ingo Br?ckl <ib wupperonline de>
To: gtk-devel-list gnome org
Subject: Re: gdk-pixbuf: Add IANA registered image/emf and image/wmf
Message-ID: <59269c96.301d883f.bm000@wupperonline.de>
Content-Type: text/plain; charset=ISO-8859-1

> Please see

>   https://bugzilla.gnome.org/show_bug.cgi?id=782390

Ping?

These media types are being used by shared-mime-info for over 8 months.

Ingo


------------------------------

Message: 2
Date: Thu, 25 May 2017 10:55:40 +0200
From: Ingo Br?ckl <ib wupperonline de>
To: Matthias Clasen <mclasen redhat com>
Cc: gtk-devel-list gnome org
Subject: Re: Bug 554926 still in 2.24.31
Message-ID: <59269c96.09c4a12e.bm002@wupperonline.de>
Content-Type: text/plain; charset=ISO-8859-1

On Tue, 25 Apr 2017 13:38:22 +0200, I wrote:

> Please apply commit e3bd926c1ef83027c756488ba19f4353930fc6db to current
> GTK+ 2 (2.24.31) where it is missing.

> The bug has been described in

>   https://bugzilla.gnome.org/show_bug.cgi?id=554926

> and has been fixed on Tue, 10 Aug 2010 04:13:22 +0000 (UTC) in 2.90.5.

Someone please apply and fix it.

Ingo