<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Karl, Karl Fogel wrote: <blockquote cite="mid:87ab9rkdud.fsf@canonical.com" type="cite"> <pre wrap=""> Thoughts? Rotten tomatos? Am I onto a real problem here? </pre> </blockquote> It's a real problem.  I'm not expert, I'm just a lurker on the list (like I was on the svn lists when you were there).    We currently use svn, and I've considered converting us over to a tool like bzr.  And though I consider myself an svn "expert", I'm a bit bewildered by all the options. In addition to Karl's "getting started" use-cases, I think something that would *greatly* help the bzr adoption rate is simple guides to transitioning from other VCSs (like subversion).    There are millions of svn users out there, and simplifying the transition will definitely bring users to bzr. Some of the things I've wondered an not found simple/obvious answers to: <ul> <li>How do I convert my svn repo to bzr and then publish it?</li> <li>My svn repo contains multiple independent projects, each with their own trunk/branches/tags sub folders .... how would I convert this to bzr?  Can I have a single repository?  Or a separate one for each project? </li> <li>Which bzr repo format should I use?</li> <li>How does using a foreign branch (bzr branch <a class="moz-txt-link-freetext" href="svn://blah">svn://blah</a>) differ from converting the repo using svn-import (or svn2bzr)?  When would I choose one over the other? </li> </ul> There's scattering of information on these topics ... but it's hard to get a clear picture of the steps.   It would be great if the transition from other VCSs could also be added to your list! Cheers, Matt </body> </html>