<?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"
	>
<channel>
	<title>Comments on: What&#8217;s a hoe?</title>
	<atom:link href="http://drnicwilliams.com/2006/11/13/whats-a-hoe/feed/" rel="self" type="application/rss+xml" />
	<link>http://drnicwilliams.com/2006/11/13/whats-a-hoe/</link>
	<description>Ruby makes Rails, Javascript makes Ajax, Dr Nic makes Magic</description>
	<pubDate>Mon, 06 Oct 2008 17:07:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: sockmonk</title>
		<link>http://drnicwilliams.com/2006/11/13/whats-a-hoe/#comment-753</link>
		<dc:creator>sockmonk</dc:creator>
		<pubDate>Tue, 21 Nov 2006 22:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://drnicwilliams.com/2006/11/13/whats-a-hoe/#comment-753</guid>
		<description>The change in newgem seems great for creating a new rubyforge project, but what about the other target audience, those of us packaging gems for internal company use? Any chance of being able to generate plain old gems again?

Or, maybe better, being able to specify the gem server, probably leaving rubyforge as the default? 

Thanks,

Wes</description>
		<content:encoded><![CDATA[<p>The change in newgem seems great for creating a new rubyforge project, but what about the other target audience, those of us packaging gems for internal company use? Any chance of being able to generate plain old gems again?</p>
<p>Or, maybe better, being able to specify the gem server, probably leaving rubyforge as the default? </p>
<p>Thanks,</p>
<p>Wes</p>
]]></content:encoded>
	</item>
</channel>
</rss>
