From owner-freebsd-ports@freebsd.org Mon May 15 11:16:38 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A341BD6D41E for ; Mon, 15 May 2017 11:16:38 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61EC8C60 for ; Mon, 15 May 2017 11:16:37 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1dADzR-000KgB-20; Mon, 15 May 2017 13:16:37 +0200 Date: Mon, 15 May 2017 13:16:37 +0200 From: Kurt Jaeger To: Karli =?iso-8859-1?Q?Sj=F6berg?= Cc: freebsd-ports@freebsd.org Subject: Re: Bug report assistance Message-ID: <20170515111636.GH87900@home.opsec.eu> References: <1494845859.4961.2.camel@inparadise.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1494845859.4961.2.camel@inparadise.se> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 May 2017 11:16:38 -0000 Hi! > I would like to know what I can do to help progress a bug report > further. I have had my eyes on bug 212420 for four months now, and > proposed a solution about two months ago but I haven't gotten any > responses back so far. > > What can I do, more than adding to the bug report (that no one seems to > read), to help resolve this bug report? Posting here helps. And yes, the changes you propose are complex, so the number of committers able to work on that is smaller. If I find a quiet hour, I'll have a look but I can not promise anything. -- pi@opsec.eu +49 171 3101372 3 years to go !