From owner-freebsd-questions@FreeBSD.ORG Tue Apr 20 19:10:58 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAD67106566C; Tue, 20 Apr 2010 19:10:58 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from mail.netmusician.org (dorian.netmusician.org [66.244.95.101]) by mx1.freebsd.org (Postfix) with ESMTP id BFDF68FC1C; Tue, 20 Apr 2010 19:10:58 +0000 (UTC) Received: from localhost (unknown [127.0.0.1]) by mail.netmusician.org (Postfix) with ESMTP id EEBE3B906; Tue, 20 Apr 2010 15:10:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at netmusician.org Received: from mail.netmusician.org ([127.0.0.1]) by localhost (dorian.netmusician.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ETGHzuY5pcdP; Tue, 20 Apr 2010 15:10:57 -0400 (EDT) Received: from Shakti.local (c-67-176-145-181.hsd1.in.comcast.net [67.176.145.181]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.netmusician.org (Postfix) with ESMTPSA id E5190B905; Tue, 20 Apr 2010 15:10:56 -0400 (EDT) Message-ID: <4BCDFC3B.5010600@netmusician.org> Date: Tue, 20 Apr 2010 15:10:51 -0400 From: Joe Auty User-Agent: Postbox 1.1.4 (Macintosh/20100408) MIME-Version: 1.0 To: glarkin@FreeBSD.org References: <20100419185300.55218.qmail@joyce.lan> <4BCCAA33.5040500@FreeBSD.org> <4BCCAE5E.2060407@netmusician.org> <4BCCB9EE.9030503@FreeBSD.org> <4BCDF7C9.9090303@netmusician.org> <4BCDF94A.2070302@FreeBSD.org> In-Reply-To: <4BCDF94A.2070302@FreeBSD.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: John Levine , freebsd-questions@freebsd.org Subject: Re: Questions about port revision numbers, portsnap, csup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2010 19:10:59 -0000 Greg, After applying the update (which I noticed was available immediately after my last response to you, sorry about that!), everything is just peachy now, or at least not causing the segfaults, thanks! Not to sound unappreciative and purely in the spirit of being constructive, I'd suggest a little more specificity as far as what a "break" is on the commit history. This goofy title was created because it didn't occur to me that the break fix committed on April 12 was only for compilation. I would suggest specifying whether the break and the fix is for compiling, or for the software to work properly post-compilation. This would have saved me a little confusion and time. Again, you kick ass, in no way do I want this to sound harshly critical, I hope this can be taken as purely constructive :) Thanks again for your help with this fix!