From owner-cvs-doc@FreeBSD.ORG Wed May 18 15:24:09 2011 Return-Path: Delivered-To: cvs-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E74C106566B; Wed, 18 May 2011 15:24:09 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id 2CB2D8FC12; Wed, 18 May 2011 15:24:08 +0000 (UTC) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4IFO5cW026504; Wed, 18 May 2011 11:24:05 -0400 (EDT) Received: from dhcp-64-102-208-164.cisco.com (dhcp-64-102-208-164.cisco.com [64.102.208.164]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4IFO3ws027761; Wed, 18 May 2011 11:24:04 -0400 (EDT) Message-ID: <4DD3E493.8010201@freebsd.org> Date: Wed, 18 May 2011 11:24:03 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Jason Helfman References: <201105141806.p4EI6upK087278@repoman.freebsd.org> <4DCEEA98.4090300@FreeBSD.org> <800a75fbf37a5bf34858274adf2b5cb5.squirrel@mail.experts-exchange.com> In-Reply-To: <800a75fbf37a5bf34858274adf2b5cb5.squirrel@mail.experts-exchange.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bapt , Doug Barton , doc-committers@freebsd.org, cvs-all@freebsd.org, cvs-doc@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.sgml X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 15:24:09 -0000 On 5/17/11 10:40 AM, Jason Helfman wrote: > I put this patch in due to COMMENT being cut off at 60 characters. That makes sense, but given that we have other tools and sites that provide port information, is it better to recommend the shorter COMMENT that may not be sufficient to give a port intro, or should we opt for a slightly longer string? How will pkgng handle this? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome