<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Gnome rocks</title>
	<atom:link href="http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/</link>
	<description>Just another GNOME Blogs weblog</description>
	<lastBuildDate>Fri, 20 Nov 2009 09:10:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Daniel Schierbeck</title>
		<link>http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/comment-page-1/#comment-164</link>
		<dc:creator>Daniel Schierbeck</dc:creator>
		<pubDate>Wed, 30 Jan 2008 16:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/#comment-164</guid>
		<description>Where should I send a Danish translation?</description>
		<content:encoded><![CDATA[<p>Where should I send a Danish translation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: otte</title>
		<link>http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/comment-page-1/#comment-163</link>
		<dc:creator>otte</dc:creator>
		<pubDate>Wed, 30 Jan 2008 11:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/#comment-163</guid>
		<description>Importing git into svn is a pain. Don&#039;t do it if you can avoid it.
Here&#039;s how we did it:
1) Create a linear branch:
- git-rev-list HEAD &gt; revs
- Create a new from-scratch branch named &quot;linear&quot;
- for rev in `cat revs`; do git-cherrypick $rev; done
  (This won&#039;t work with that script as you have to do merges manually sometimes, but you get the idea)
- to test, git diff linear and master to be sure they are identical
2) Use tailor to import the linear branch into svn
3) Fix up authors etc
This worked because we didn&#039;t have a complex tangled mess of commits, but a pretty linear branch structure. Otherwise you&#039;ll end up banging your head against your desk way too often when trying to create the linear branch.</description>
		<content:encoded><![CDATA[<p>Importing git into svn is a pain. Don&#8217;t do it if you can avoid it.<br />
Here&#8217;s how we did it:<br />
1) Create a linear branch:<br />
- git-rev-list HEAD &gt; revs<br />
- Create a new from-scratch branch named &#8220;linear&#8221;<br />
- for rev in `cat revs`; do git-cherrypick $rev; done<br />
  (This won&#8217;t work with that script as you have to do merges manually sometimes, but you get the idea)<br />
- to test, git diff linear and master to be sure they are identical<br />
2) Use tailor to import the linear branch into svn<br />
3) Fix up authors etc<br />
This worked because we didn&#8217;t have a complex tangled mess of commits, but a pretty linear branch structure. Otherwise you&#8217;ll end up banging your head against your desk way too often when trying to create the linear branch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anonim</title>
		<link>http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/comment-page-1/#comment-162</link>
		<dc:creator>anonim</dc:creator>
		<pubDate>Wed, 30 Jan 2008 11:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/otte/2008/01/30/gnome-rocks/#comment-162</guid>
		<description>How did you import you git repo into svn? Did it actually mantained the full git history?

thanks</description>
		<content:encoded><![CDATA[<p>How did you import you git repo into svn? Did it actually mantained the full git history?</p>
<p>thanks</p>
]]></content:encoded>
	</item>
</channel>
</rss>
