Date: Fri, 9 Jul 2010 09:34:46 +0200 From: Gary Jennejohn <gljennjohn@googlemail.com> To: Peter Jeremy <peterjeremy@acm.org> Cc: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/cutting-edge chapter.sgml Message-ID: <20100709093446.4d4decab@ernst.jennejohn.org> In-Reply-To: <20100709061311.GB34250@server.vk2pj.dyndns.org> References: <201007071523.o67FNVEX005939@repoman.freebsd.org> <alpine.BSF.2.00.1007072019290.75167@woozle.rinet.ru> <4C34AE6C.2020204@FreeBSD.org> <20100707192907.5895644e@ernst.jennejohn.org> <20100709061311.GB34250@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 9 Jul 2010 16:13:12 +1000 Peter Jeremy <peterjeremy@acm.org> wrote: > On 2010-Jul-07 19:29:07 +0200, Gary Jennejohn <gljennjohn@googlemail.com> wrote: > >What it can't do is act like cvsupd. It can maintain a local CVS > >repository, I use it for that, but I have to use cvsupd to update > >my ports and src trees from the local repository. > > If you have a local CVS repository, why not use CVS to update your > local src and ports trees? You can always NFS export it to other > hosts and FreeBSD's CVS supports read-only repositories. > OK, I don't _have to_ use cvsupd, but I'm lazy and cvsupd automagically handles the updates for me. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100709093446.4d4decab>