From owner-freebsd-doc@FreeBSD.ORG Mon Nov 29 15:53:49 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D30F16A4CE; Mon, 29 Nov 2004 15:53:49 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81AA843D3F; Mon, 29 Nov 2004 15:53:48 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iATFrkUV025445; Mon, 29 Nov 2004 17:53:46 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iATFrkZY005728; Mon, 29 Nov 2004 17:53:46 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)iATFrk42005727; Mon, 29 Nov 2004 17:53:46 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Mon, 29 Nov 2004 17:53:45 +0200 From: Giorgos Keramidas To: Nik Clayton Message-ID: <20041129155345.GA5676@orion.daedalusnetworks.priv> References: <20041128202656.GL750@zaphod.nitro.dk> <20041129060320.GA26868@clan.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041129060320.GA26868@clan.nothing-going-on.org> cc: freebsd-doc@freebsd.org cc: "Simon L. Nielsen" Subject: Re: Doc BoF at EuroBSDCon X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 15:53:49 -0000 On 2004-11-29 06:03, Nik Clayton wrote: > On Sun, Nov 28, 2004 at 09:26:57PM +0100, Simon L. Nielsen wrote: > > - To be as little disruptive as possible to normal doc work it was > > suggested to branch the doc/ tree for the work, and do the work in a > > separate branch, to be merged into the main branch later again. > > Rather than branch it in CVS I'd say use Perforce for this work. Yes please, Perforce seems a natural place for this. Experimenting with things like moving files or entire trees around, creating new files within the branch or other stuff that CVS would make a real PITA, are done easier in Perforce and will not force everyone who keeps CVS mirrors to update a bazillion files while the work is still in progress.