Databases
StackOverflow2013
Postsdbo
PO
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You shouldn't use Subversion directly to checkout the code. Use Bazaar to do it. For example</p> <pre><code>bzr svn-import http://feedparser.googlecode.com/svn/ feedparser cd feedparser bzr branch trunk mybranch cd mybranch bzr checkout # hack... </code></pre> <p>Check <a href="http://doc.bazaar.canonical.com/latest/en/user-guide/svn_plugin.html" rel="nofollow">the documentation</a>, the <a href="http://wiki.bazaar.canonical.com/BzrMigration#bzr-svn" rel="nofollow">Subversion Migration page</a> on the bzr wiki, and <code>bzr help svn-import</code> for more details.</p> <p>To address your second question</p> <blockquote> <p>does svn support local repositories like bzr</p> </blockquote> <p>Subversion is based off of a server-client model, whereas in distributed VCSes like git, bzr, and Mercurial, it's all sort of rolled into one. You <em>can</em> have a Subversion server running locally, however, an SVN repository should be served by one, and <em>only</em> one SVN server. With a distributed VCS, you clone an <em>entire</em> repository (or at least a branch, in bzr's case), meaning that you have all the data and metadata necessary for you to serve up your clone and have other people clone from you. Unlike distributed VCSes, you do not create an entire copy of the repository locally when you do <code>svn checkout</code>; you only create local <em>working copies</em> of the repository, which is the files under revision control and some (but not all) of the metadata. A working local copy of a SVN repository is insufficient to act as a repository itself; you can not put that working copy on a server and let other people do checkouts from it.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload