From owner-freebsd-ports@FreeBSD.ORG Fri Oct 31 17:25:26 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 59D6DB67 for ; Fri, 31 Oct 2014 17:25:26 +0000 (UTC) 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 1B33510C for ; Fri, 31 Oct 2014 17:25:25 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XkFwz-000Gui-0o; Fri, 31 Oct 2014 18:25:25 +0100 Date: Fri, 31 Oct 2014 18:25:24 +0100 From: Kurt Jaeger To: Robert Backhaus Subject: Re: Bug 193424 has no been committed - why? Message-ID: <20141031172524.GJ66862@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2014 17:25:26 -0000 Hi! > As the maintainer, I gave the go-ahead for this PR to be committed well > over a month ago. I sent a message to koobs@ to see why it wasn't > committed, and have not received a reply. > > Can a committer please take this and commit it, or tell me what I need to > do to get it committed? I dont speak for koobs@, but I assume from the PRs I'm trying to work on that it's mostly overload on the side of the committers, in general. -- pi@opsec.eu +49 171 3101372 6 years to go !