Date: Mon, 29 Nov 2004 17:53:45 +0200 From: Giorgos Keramidas <keramida@freebsd.org> To: Nik Clayton <nik@freebsd.org> Cc: "Simon L. Nielsen" <simon@freebsd.org> Subject: Re: Doc BoF at EuroBSDCon Message-ID: <20041129155345.GA5676@orion.daedalusnetworks.priv> In-Reply-To: <20041129060320.GA26868@clan.nothing-going-on.org> References: <20041128202656.GL750@zaphod.nitro.dk> <20041129060320.GA26868@clan.nothing-going-on.org>
index | next in thread | previous in thread | raw e-mail
On 2004-11-29 06:03, Nik Clayton <nik@freebsd.org> 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.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041129155345.GA5676>