migrating from CVS

[Erik Bågfors]

2006/3/6, Jos Backus <jos at catnook.com>:
> - Size of the source code base Bazaar-NG can handle reliably without slowing
>   down to a crawl. How safe is it to migrate a CVS repository with a dozen or
>   so modules containing thousands of files each? Has Bazaar-NG been tested
>   against such large repositories?

This is halfway of topic, but still.
In cvs the repository is the location where you have to go to find anything.  So
cvs -d$repo checkout module/whatever
cvs -d$repo checkout module/another

etc

In svn or bzr you don't have to point into the repository, but rather
what you want to checkout.  For example

svn checkout svn://host/path/to/module/trunk
svn checkout svn://host/path/to/module/branches/1.0
bzr checkout sftp://host/path/to/module/trunk
bzr checkout sftp://host/path/to/module/branches/1.0

The question now, is, where is your repository?  Well, the nice thing
is that it can be in "path", or it can be in "to", or it can be in
"module".  It makes no difference to the user.

What this also means is that you can put your repository wherever you
want along the path.

When my company moved from cvs to svn, this meant that instead of one
large repository, that the user needs to know about, we keep many
smaller once, that the user doesn't really have to know about.  It's
easier to manage/take backups/etc.  This is true for both svn and bzr
I belive.  Of course, you can put everything into one large repository
if you like and both svn and bzr should handle it just fine, but there
might be other reasons outside of the actual VCS, to why you'd prefer
many repositories.

Regards,
Erik