better explanation of import process
Bug #130573 reported by
Martin Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Low
|
Unassigned |
Bug Description
There are several ways you can get an import from an existing cvs or svn branch into Bazaar. We should give a better explanation of them on the web site. In this approximate order:
0- talk to us
1- conversion on launchpad
2- cvsps - may not be deterministic
3- if you have an svn repo, use bzr-svn
4- svn2bzr - intended for one direction, one-off conversions. Any remaining advantages over bzr-svn?
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
On Mon, 2007-08-06 at 03:41 +0000, Martin Pool wrote:
> Public bug reported:
>
> There are several ways you can get an import from an existing cvs or svn
> branch into Bazaar. We should give a better explanation of them on the
> web site. In this approximate order:
>
> 0- talk to us
> 1- conversion on launchpad
> 2- cvsps - may not be deterministic
> 3- if you have an svn repo, use bzr-svn
> 4- svn2bzr - intended for one direction, one-off conversions. Any remaining advantages over bzr-svn?
svn2bzr creates deterministic revision ids so doesn't necessarily have
to be used for one-off conversions, using it incrementally also works.
"bzr svn-import" from bzr-svn and svn2bzr basically have the same
functionality, except:
* svn2bzr does proper renames rather than delete+add.
* bzr-svn can use local or remote repositories and svn dump files,
svn2bzr only works with svn dump files
* bzr-svn can guess the branching scheme
I'm very confident about the stability of bzr-svn's import functionality
and last time I checked svn2bzr also worked very well (though I haven't
tested it on a wide range of repositories, maybe Gustavo can comment on
that?)
Cheers,
Jelmer