2012-01-17T21:54:19-08:00 http://davedash.com/ Dave Dash dd+atom1@davedash.com 2008-07-22T00:00:00-07:00 http://davedash.com/2008/07/22/creating-a-new-project-in-mercurial-versus-svn <p>One of the most annoying things about creating new SVN projects is the new project dance:</p> <pre><code>$ svnadmin create $SVNREP_DIR/newproject $ svn mkdir -m "layout creation" file:///$SVNREP_DIR/newproject/trunk file:///$SVNREP_DIR/newproject/tags file:///$SVNREP_DIR/newproject/branches $ mkdir newproject $ cd newproject $ svn import -m "initial import" . file:///$SVNREP_DIR/newproject/trunk </code></pre> <p>Oh... yeah, no this isn't that bad.</p> <p>It's this part that's bad:</p> <pre><code>$ cd .. $ mv newproject newproject.tmp $ svn co file:///$SVNREP_DIR/newproject/trunk newproject $ # do sanity check here... $ rm -rf newproject.tmp </code></pre> <p>That's a lot of work, and it's actually hard to remember unless you do it a lot.</p> <p>Here's the mercurial equivalent:</p> <pre><code>$ mkdir -p newproject/trunk $ cd newproject $ mkdir branches tags $ hg init </code></pre> <p>That's it. It's not apples to apples of course. Mercurial keeps its repository locally, and does very simple push/pull commands for synchronization. But the dreaded dance of removing a project after it's been imported and then checking out the project is really a peeve of mine.</p>