<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Svn on Nikhil&#39;s blog</title>
    <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/svn/</link>
    <description>Recent content in Svn on Nikhil&#39;s blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 02 Aug 2009 11:26:00 +0000</lastBuildDate>
    <atom:link href="https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/svn/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introducing Cq</title>
      <link>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/introducing-cq/</link>
      <pubDate>Sun, 02 Aug 2009 11:26:00 +0000</pubDate>
      <guid>https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2009/introducing-cq/</guid>
      <description>Cq ( Commit Queue ) is a bridge between Mercurial and Subversion. Its whole objective is to allow you to work offline on Subversion repositories, but continue doing atomic commits. Useful when you are on the move and don&#39;t have internet access.&#xA;The premise is that you copy the working copy into a Mercurial repository. Hack away in the repository, and commit to the repository. Once you are back online, run cq commit to actually commit the changes to the Subversion repository.</description>
    </item>
  </channel>
</rss>
