<br><div class="gmail_quote"><div class="gmail_quote">Sorry to spam the list about an individual bug, but this is an important issue for Sugar, and I don't know how else to get a response. Again, I'll try to apply the old patch, if I can get some response that it would be integrated into a new version. But this is not so important that we'd be willing to carry the patch in Sugar, or fork Xephyr. So I wanted to check first, because if nobody will check it in, I'd rather save the time.<br> <br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Jameson Quinn</b> <span dir="ltr"><<a href="mailto:jameson.quinn@gmail.com" target="_blank">jameson.quinn@gmail.com</a>></span><br> Date: Mon, Mar 23, 2009 at 11:10 AM<br>Subject: xephyr bug 19365<br>To: <a href="mailto:mallum@openedhand.com" target="_blank">mallum@openedhand.com</a><br><br><br>You're the asignee for bug 19365 : <a href="http://bugs.freedesktop.org/show_bug.cgi?id=19365" target="_blank">http://bugs.freedesktop.org/show_bug.cgi?id=19365</a>. I realize that you probably have many bugs like that auto-assigned to you and cannot take an interest in all of them. I was wondering what I could do to help this bug find a real owner. I'm not really into that kind of programming, but if necessary I could see what I can do to apply the patch that Sascha Silbe found to a current version of xephyr. But I don't want to do that if the bug will nevertheless languish.<br> <br>Thanks, and sorry to bother you,<br><font color="#888888">Jameson<br> </font></div><br> <br></div><br> </div><br>