From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id E5D8A13832E for ; Thu, 11 Aug 2016 04:05:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5F52621C09F; Thu, 11 Aug 2016 04:05:01 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8C5DF21C099 for ; Thu, 11 Aug 2016 04:05:00 +0000 (UTC) Received: from pc1 (c-50-148-132-189.hsd1.ca.comcast.net [50.148.132.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: hanno) by smtp.gentoo.org (Postfix) with ESMTPSA id 178F3340A60; Thu, 11 Aug 2016 04:04:59 +0000 (UTC) Date: Wed, 10 Aug 2016 20:16:24 -0700 From: Hanno =?UTF-8?B?QsO2Y2s=?= To: Pacho Ramos Cc: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Empty project: LXDE Message-ID: <20160810201624.5fed8cb9@pc1> In-Reply-To: <1470558148.17315.118.camel@gentoo.org> References: <1470558148.17315.118.camel@gentoo.org> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 2f91bd03-eb68-4531-a55d-457dadddfa60 X-Archives-Hash: a72d764341df2321ddf0bec958b12099 On Sun, 07 Aug 2016 10:22:28 +0200 Pacho Ramos wrote: > Now=C2=A0https://wiki.gentoo.org/wiki/Project:LXDE=C2=A0is empty >=20 > Feel free to join, anyway, if I don't misremember, LXDE is dead for a > long time in favor of LXQT... in that case treecleaning the packages > would also be an option Oh... I'm actually using lxde and I have recently pushed a bunch of memory safety fixes to upstream that were a result of my address sanitizer testing. LXDE upstream isn't totally dead, occasionally releases with fixes happen, yet they're slow. I'll look that I maintain some of the stuff, yet I'd prefer if I'd be not the only one. --=20 Hanno B=C3=B6ck https://hboeck.de/ mail/jabber: hanno@hboeck.de GPG: BBB51E42