Date: Tue, 20 Apr 2010 15:10:51 -0400 From: Joe Auty <joe@netmusician.org> To: glarkin@FreeBSD.org Cc: John Levine <johnl@iecc.com>, freebsd-questions@freebsd.org Subject: Re: Questions about port revision numbers, portsnap, csup Message-ID: <4BCDFC3B.5010600@netmusician.org> In-Reply-To: <4BCDF94A.2070302@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BCDFC3B.5010600>