<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Fun-killers: Four players who could have made today&#8217;s free agent frenzy more exciting</title>
	<atom:link href="http://prohockeytalk.nbcsports.com/2011/07/01/fun-killers-four-players-who-could-have-made-todays-free-agent-frenzy-more-exciting/feed/" rel="self" type="application/rss+xml" />
	<link>http://prohockeytalk.nbcsports.com/2011/07/01/fun-killers-four-players-who-could-have-made-todays-free-agent-frenzy-more-exciting/</link>
	<description>ProHockeyTalk on NBCSports.com</description>
	<lastBuildDate>Fri, 24 May 2013 20:47:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: finodelfino</title>
		<link>http://prohockeytalk.nbcsports.com/2011/07/01/fun-killers-four-players-who-could-have-made-todays-free-agent-frenzy-more-exciting/comment-page-1/#comment-13350</link>
		<dc:creator><![CDATA[finodelfino]]></dc:creator>
		<pubDate>Fri, 01 Jul 2011 15:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://prohockeytalk.nbcsports.com/?p=41940#comment-13350</guid>
		<description><![CDATA[I&#039;m sure Tampa would be more than willing to unload vinny lecalvier&#039;s retirement contract. They will need the cap space to counter stammer&#039;s offer sheet he will receive from at least 20 teams.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m sure Tampa would be more than willing to unload vinny lecalvier&#8217;s retirement contract. They will need the cap space to counter stammer&#8217;s offer sheet he will receive from at least 20 teams.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
