From owner-cvs-doc@FreeBSD.ORG Wed Jul 7 17:43:18 2010 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 BFF9C1065670 for ; Wed, 7 Jul 2010 17:43:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 4E9668FC1E for ; Wed, 7 Jul 2010 17:43:17 +0000 (UTC) Received: (qmail 20546 invoked by uid 399); 7 Jul 2010 17:43:15 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 7 Jul 2010 17:43:15 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C34BCB2.8090909@FreeBSD.org> Date: Wed, 07 Jul 2010 10:43:14 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Johann Kois References: <201007071523.o67FNVEX005939@repoman.freebsd.org> <4C34AE6C.2020204@FreeBSD.org> In-Reply-To: <4C34AE6C.2020204@FreeBSD.org> X-Enigmail-Version: 1.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc-committers@FreeBSD.org, Dmitry Morozovsky , cvs-all@FreeBSD.org, cvs-doc@FreeBSD.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/cutting-edge chapter.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, 07 Jul 2010 17:43:18 -0000 On 7/7/2010 9:42 AM, Johann Kois wrote: > > If I remember correctly cvsup does some things csup can not do. > Handling a local cvsup repository, for example. If you're going to update the documentation it's kind of important that you know these kinds of facts first. :) For some time now csup has been a drop-in replacement for all of the client functions of cvsup. The only thing it doesn't have is a GUI. > If we do not mention cvsup here anymore than we would need to get rid of > cvsup in the whole chapter AND in the "Using CVSup" chapter of the > handbook. I posted something about this to -doc a little while ago suggesting that the way to handle it is to flip the places of csup and cvsup in the docs. That is, where csup is mentioned as an aside now and cvsup mentioned in the main body of the docs and examples their positions should be swapped. The few comments in response to that suggestion were positive. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/