From owner-freebsd-ports@FreeBSD.ORG Tue Dec 17 22:34:27 2013 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 786B1F80 for ; Tue, 17 Dec 2013 22:34:27 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 51BAB13E4 for ; Tue, 17 Dec 2013 22:34:24 +0000 (UTC) Received: from [192.168.1.14] (ip70-178-7-237.ks.ks.cox.net [70.178.7.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 95D7E435A3 for ; Tue, 17 Dec 2013 16:34:05 -0600 (CST) Message-ID: <52B0D149.5020308@marino.st> Date: Tue, 17 Dec 2013 23:33:45 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "ports@FreeBSD.org" Subject: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 22:34:27 -0000 Over the months I've seen several ports users copy a failure log and mail it to ports@, usually without even saying "hello". I've tried to discourage that behavior but other members of this mail list encourage this method of bypassing writing PRs. One user even proudly boasted that sending email to ports@ is faster than writing a PR so of course he was going to do that instead. If this kind of post is acceptable to the rest of the people here, and I'm alone in not only finding it very rude, but also making the volume of ports@ too high, then please tell me that the problem is with me. If nothing is going to change, I am going to unsubscribe from ports@ list. The gcc developers on gcc@gcc.gnu.org always tell a poster when a post in appropriate for that list and as a result and as a result the posters usually only make a mistake once. I'd like to see something closer to that, but if the list isn't going to be policed then it's too noisy for me. John