<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Git on Insignificant Bits</title>
    <link>https://bobcopeland.com/blog/tags/git/</link>
    <description>Recent content in Git on Insignificant Bits</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 09 Apr 2009 15:00:46 +0000</lastBuildDate>
    <atom:link href="https://bobcopeland.com/blog/tags/git/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Manual git-svn clone</title>
      <link>https://bobcopeland.com/blog/2009/04/manual-git-svn-clone/</link>
      <pubDate>Thu, 09 Apr 2009 15:00:46 +0000</pubDate>
       <guid isPermaLink="false">http://bobcopeland.com/blog/?p=1290</guid> 
      <description>&lt;p&gt;I finally decided to do something about the five independent git trees I had on my hard drive at work. The problem is they are all really branches of the same subversion repository, and moving patches back and forth between them meant I had added them all as git remotes to each other. The meta problem is that we didn&amp;rsquo;t always branch off of the same trunk directory, from back when we were drinking the &amp;ldquo;just snapshots of directories&amp;rdquo; subversion kool-aid, so &lt;code&gt;git svn clone&lt;/code&gt; doesn&amp;rsquo;t do the right thing for our branches.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
