← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/en/admin-guide/migration.txt

  • Committer: Andrew Bennetts
  • Date: 2010-08-17 06:45:33 UTC
  • mfrom: (5050.17.9 2.2)
  • mto: This revision was merged to the branch mainline in revision 5379.
  • Revision ID: andrew.bennetts@canonical.com-20100817064533-kof2i2f3r6mr4ayb
Merge lp:bzr/2.2 into lp:bzr, including fixes for #192859, #224373, #300062, #585667, #614404, #617503.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/admin-guide/migration.txt
3
3
 
4
4
Migrating between version control systems can be a complicated process, and
5
5
Bazaar has extensive documentation on the process at 
6
 
http://doc.bazaar-vcs.org/migration/en and we won't attempt to repeat that
 
6
http://doc.bazaar.canonical.com/migration/en and we won't attempt to repeat that
7
7
here.  We will try to give a few motivating examples for conversion from
8
8
Mercurial and Subversion.
9
9
 
47
47
Bazaar's `svn`_ plugin provides tools for interaction with Subversion
48
48
projects.  In fact, Bazaar can be used transparently with projects stored in
49
49
Subversion, but that is beyond the scope of this document.  (See
50
 
http://doc.bazaar-vcs.org/en/migration/foreign/bzr-on-svn-projects.html for
 
50
http://doc.bazaar.canonical.com/en/migration/foreign/bzr-on-svn-projects.html for
51
51
more on that subject.)  What is relevant here is the ``svn-import`` command
52
52
provided by that plugin.  This can import an entire subversion repository
53
53
including tags and branches, particularly if they are stored in Subversion's