Date: Mon, 9 Feb 2004 16:14:24 -0500 From: Alexander Kabaev <ak03@gte.com> To: des@des.no (Dag-Erling Sm_rgrav) Cc: freebsd-hackers@freebsd.org Subject: Re: Subversion/CVS experiment summary Message-ID: <20040209161424.723c8bef@kanpc.gte.com> In-Reply-To: <xzpekt4xcmu.fsf@dwp.des.no> References: <200402091130.05656.craig@tobuj.gank.org> <20040209175314.GU2803@pcwin002.win.tue.nl> <xzpr7x4xf3g.fsf@dwp.des.no> <20040209140552.340b75d5@kanpc.gte.com> <xzpekt4xcmu.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 09 Feb 2004 20:43:05 +0100 des@des.no (Dag-Erling Sm_rgrav) wrote: > Alexander Kabaev <ak03@gte.com> writes: > > cvs-to-perforce scripts use DB files to keep an information on > > related commits while they scan CVS repo. I didn't try FreeBSD CVS, > > but whole SGI Linux tree with full history was processed quite > > effortlessly, without running out of memory. > > Perforce uses CVS as backing store, so I expect matters are a little > different than for SVN. > There are two versions of cvs2p4 script and one of them populates repository using p4 commands. Either way, both versions require full scan of source repository to locate related changes and group them together. So matters are not that different for SVN. -- Alexander Kabaev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209161424.723c8bef>