<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.5" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>Ned Ludd - Latest comments on cvs2git/parsecvs gentoo-x86 conversion</title>
		<link>http://blogs.gentoo.org/solar?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.5"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: cvs2git/parsecvs gentoo-x86 conversion</title>
			<pubDate>Sun, 02 Jul 2006 13:24:18 +0000</pubDate>
			<dc:creator>solar [Member]</dc:creator>
			<guid isPermaLink="false">c13445@http://blogs.gentoo.org/</guid>
			<description>We got Alec Warner access to another power5 and he's been finishing out his testing on his own. I know one of the tools 'tailor' he was testing with was looking like it was going to take the better part of ~30 days to complete.</description>
			<content:encoded><![CDATA[We got Alec Warner access to another power5 and he's been finishing out his testing on his own. I know one of the tools 'tailor' he was testing with was looking like it was going to take the better part of ~30 days to complete.]]></content:encoded>
			<link>http://blogs.gentoo.org/solar/2006/06/12/cvs2git_parsecvs_gentoo_x86_conversion#c13445</link>
		</item>
				<item>
			<title>In response to: cvs2git/parsecvs gentoo-x86 conversion</title>
			<pubDate>Mon, 12 Jun 2006 16:30:55 +0000</pubDate>
			<dc:creator>Jordi Vilalta [Visitor]</dc:creator>
			<guid isPermaLink="false">c10000@http://blogs.gentoo.org/</guid>
			<description>I don't know how cvs2git works, but maybe you should try tailor (http://packages.gentoo.org/packages/?category=dev-util;name=tailor). I think it works in an incremental way, reproducing one patchset at a time (which should be runnable on &quot;normal&quot; machines), allowing for bidirectional sync between repositories. It has a lot of backends, so you can try other VCS instead of git, to see how much space does the same tree take up in each VCS.&lt;br /&gt;
&lt;br /&gt;
Good luck!</description>
			<content:encoded><![CDATA[I don't know how cvs2git works, but maybe you should try tailor (http://packages.gentoo.org/packages/?category=dev-util;name=tailor). I think it works in an incremental way, reproducing one patchset at a time (which should be runnable on "normal" machines), allowing for bidirectional sync between repositories. It has a lot of backends, so you can try other VCS instead of git, to see how much space does the same tree take up in each VCS.<br />
<br />
Good luck!]]></content:encoded>
			<link>http://blogs.gentoo.org/solar/2006/06/12/cvs2git_parsecvs_gentoo_x86_conversion#c10000</link>
		</item>
				<item>
			<title>In response to: cvs2git/parsecvs gentoo-x86 conversion</title>
			<pubDate>Mon, 12 Jun 2006 04:27:00 +0000</pubDate>
			<dc:creator>Corey [Visitor]</dc:creator>
			<guid isPermaLink="false">c9944@http://blogs.gentoo.org/</guid>
			<description>the need for 64bit counters for the memory stats is a good problem to have!!&lt;br /&gt;
&lt;br /&gt;
:D</description>
			<content:encoded><![CDATA[the need for 64bit counters for the memory stats is a good problem to have!!<br />
<br />
:D]]></content:encoded>
			<link>http://blogs.gentoo.org/solar/2006/06/12/cvs2git_parsecvs_gentoo_x86_conversion#c9944</link>
		</item>
			</channel>
</rss>
