<?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: Ferrari waiting list up to three years for 599 GTB and 430</title>
	<atom:link href="http://ferrari-news.com/2008/02/16/ferrari-waiting-list-up-to-three-years-for-599-gtb-and-430/feed/" rel="self" type="application/rss+xml" />
	<link>http://ferrari-news.com/2008/02/16/ferrari-waiting-list-up-to-three-years-for-599-gtb-and-430/</link>
	<description>News on Ferrari continually updated from thousands of sources around the net</description>
	<lastBuildDate>Sun, 01 Nov 2009 21:48:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Spy Shots: First longer-wheelbase Ferrari 612 Scaglietti replacement spotted &#124; Latest Ferrari News</title>
		<link>http://ferrari-news.com/2008/02/16/ferrari-waiting-list-up-to-three-years-for-599-gtb-and-430/#comment-209</link>
		<dc:creator>Spy Shots: First longer-wheelbase Ferrari 612 Scaglietti replacement spotted &#124; Latest Ferrari News</dc:creator>
		<pubDate>Sun, 01 Nov 2009 21:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://ferrari-news.com/2008/02/16/ferrari-waiting-list-up-to-three-years-for-599-gtb-and-430/#comment-209</guid>
		<description>[...] about. It still sports the hood scoop (bigger engine with more power, anyone?) and California-style stacked tailpipes, and it looks like it might have a longer wheelbase to [...]</description>
		<content:encoded><![CDATA[<p>[...] about. It still sports the hood scoop (bigger engine with more power, anyone?) and California-style stacked tailpipes, and it looks like it might have a longer wheelbase to [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

