<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Out of my mind...: Tag mercurial</title>
    <link>http://blog.fredjean.net/articles/tag/mercurial</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Frederic Jean's Random Thoughts</description>
    <item>
      <title>Creating a Remote Mercurial Repository</title>
      <description>&lt;p&gt;I wanted to play with the metaprogramming abilities of Groovy. So I started a new project in NetBeans and created a Mercurial repository to version it. I had a few files committed eventually.&lt;/p&gt;
&lt;p&gt;I am really nervous about keeping code in a single location. This is why I do Time Machine backups on my mac. This is also why I keep a clone of Mercurial repositories on my workstation at work. Well, except for my personal projects. I keep a clone on the same server that is hosting this blog. I decided that this new project was worth cloning remotely.&lt;/p&gt;
&lt;p&gt;It turns out that you can clone a repository to a remote system just as easily that you can clone a repository from a remote system. The syntax is simply:&lt;/p&gt;&lt;code&gt;hg clone [local-repo] [remote-repo]&lt;/code&gt; &lt;span style="font-family: Monaco;"&gt;&lt;br /&gt;&lt;/span&gt;
&lt;p&gt;This even works over ssh. It also leads to a little more peace of mind on my part.&lt;/p&gt;


</description>
      <pubDate>Mon, 14 Jan 2008 07:04:06 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:6bf8198b-1d16-4abe-8b8e-6e5fd60d801a</guid>
      <author>fred@fredjean.net (Frederic Jean)</author>
      <link>http://blog.fredjean.net/articles/2008/01/14/creating-a-remote-mercurial-repository</link>
      <category>Personal</category>
      <category>General</category>
      <category>mercurial</category>
      <category>hg</category>
    </item>
  </channel>
</rss>
