Re: PyGTK again (was: Apologize and to take PyGTK)

2013-04-05 Thread Christian Kirbach
Am Freitag, den 05.04.2013, 03:23 +0800 schrieb Xiaojun Ma: I'm trying to take the maintenance of PyGTK, sent an E-mail to previous maintainers. I got the E-mail addresses with the help of Stef Walter and Dieter Verfaillie, thank you for your information.

RE: PyGTK again (was: Apologize and to take PyGTK)

2013-04-04 Thread Xiaojun Ma
For those who concern the technical issue around of the memory leak issue of PyGTK, any older, virtually equivalent but unnoticed bug/patch combination is found: s/any/an ___ desktop-devel-list mailing list

Re: PyGTK again (was: Apologize and to take PyGTK)

2013-04-04 Thread Andreas Nilsson
On 2013-04-04 16:23, Xiaojun Ma wrote: As I keep getting Your message to desktop-devel-list awaits moderator approval while some messages out some don't without any private notice. I decided to use new attitude and mailbox :) That's wonderful news! The moderation flag for your other e-mail

Re: PyGTK again (was: Apologize and to take PyGTK)

2013-04-04 Thread Mike
Hi I'm glad to see both side of you calm down . I feel that this could be a typical misunderstanding between users, package maintainers and the upstream developers. Could we do anything about this? I suggest we could setup a activity graph for each modules in the git repository. So people could

Re: PyGTK again (was: Apologize and to take PyGTK)

2013-04-04 Thread Germán Póo-Caamaño
On Thu, 2013-04-04 at 15:52 -0400, Mike wrote: Hi I'm glad to see both side of you calm down . I feel that this could be a typical misunderstanding between users, package maintainers and the upstream developers. Could we do anything about this? I suggest we could setup a activity graph

Re: PyGTK again (was: Apologize and to take PyGTK)

2013-04-04 Thread Alexandre Franke
On Thu, Apr 4, 2013 at 10:02 PM, Germán Póo-Caamaño g...@gnome.org wrote: On Thu, 2013-04-04 at 15:52 -0400, Mike wrote: Hi I'm glad to see both side of you calm down . I feel that this could be a typical misunderstanding between users, package maintainers and the upstream developers. Could