# [EMAIL PROTECTED] / 2004-02-12 16:48:25 -0400:
On Mon, 9 Feb 2004, Michael Reifenberger wrote:
Hi,
first, this seems to be a good analysis of SVN and a good
starting point for thinking about moving away from CVS.
I missed the original thread here, so this point may have already been
On Thu, Feb 12, 2004 at 04:48:25PM -0400, Marc G. Fournier wrote:
note that this was pre-0.34, but since its still under development,
there is always the chance that this happens again ... a load of the
system took 49hrs, I believe was mentioned ... how long to dump/reload the
system once its
On Mon, 9 Feb 2004, Michael Reifenberger wrote:
Hi,
first, this seems to be a good analysis of SVN and a good
starting point for thinking about moving away from CVS.
I missed the original thread here, so this point may have already been
made ... but ... we tried to use subversion for a
Hi,
first, this seems to be a good analysis of SVN and a good
starting point for thinking about moving away from CVS.
On Mon, 9 Feb 2004, Craig Boston wrote:
...
Comments on importing: It's SLOOW. It took 43.9 hours just for
src/sys, and this is a relatively speedy system! It starts
This is a bit of a long email, so please skip unless you're into source code
revision management :)
This is an informal report on the viability of using Subversion to manage the
FreeBSD source code repository. Some of this is generic and will be familiar
to anyone who has looked at SVN
On Mon, Feb 09, 2004 at 11:30:05AM -0600, Craig Boston wrote:
This is an informal report on the viability of using Subversion to manage the
FreeBSD source code repository. Some of this is generic and will be familiar
to anyone who has looked at SVN before, some is more FreeBSD-specific.
Stijn Hoop [EMAIL PROTECTED] writes:
I also tried refinecvs (formerly cvs2svn.pl), found at
http://lev.serebryakov.spb.ru/refinecvs/
but although it looks like it handles things much better (even vendor
branches etc), it loads EVERYTHING into memory -- which means that it
eventually grew to
On Mon, Feb 09, 2004 at 07:49:55PM +0100, Dag-Erling Sm?rgrav wrote:
Stijn Hoop [EMAIL PROTECTED] writes:
I also tried refinecvs (formerly cvs2svn.pl), found at
http://lev.serebryakov.spb.ru/refinecvs/
but although it looks like it handles things much better (even vendor
branches
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.
--
Alexander Kabaev
On Monday 09 February 2004 11:53 am, Stijn Hoop wrote:
Did you have to modify the script, or pass unusual options? I'd like to
reproduce this, but I didn't get very far when I tried a few days ago with
the 0.37.0 version of the tool.
No, I used the script as-is. The version I have is
Alexander Kabaev [EMAIL PROTECTED] 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
On Mon, Feb 09, 2004 at 01:26:45PM -0600, Craig Boston wrote:
On Monday 09 February 2004 11:53 am, Stijn Hoop wrote:
Did you have to modify the script, or pass unusual options? I'd like to
reproduce this, but I didn't get very far when I tried a few days ago with
the 0.37.0 version of the
On Mon, 09 Feb 2004 20:43:05 +0100
[EMAIL PROTECTED] (Dag-Erling Sm_rgrav) wrote:
Alexander Kabaev [EMAIL PROTECTED] 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
According to Craig Boston:
This is an informal report on the viability of using Subversion to manage the
FreeBSD source code repository. Some of this is generic and will be familiar
to anyone who has looked at SVN before, some is more FreeBSD-specific.
Thanks for doing this. I tried the
On Monday 09 February 2004 03:06 pm, Stijn Hoop wrote:
Well, that explains a lot -- for some reason I tested using
$LastChangedRevision: 7921 $. I'll try with an up-to-date one then.
I was looking through the change history for cvs2svn.py and it seems that the
0.37 version is almost exactly
15 matches
Mail list logo
