<?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: Fixing SVN Inconsistent Newlines</title>
	<atom:link href="http://blog.eflow.org/archives/130/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.eflow.org/archives/130</link>
	<description>Insert some amazingly witty tagline here</description>
	<lastBuildDate>Fri, 11 Jun 2010 13:45:56 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ben</title>
		<link>http://blog.eflow.org/archives/130/comment-page-1#comment-302</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Tue, 09 Jun 2009 13:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eflow.org/?p=130#comment-302</guid>
		<description>I used dos2unix because I just needed a standard line ending before applying CRLF.  Yes, it probably would have made more sense to use unix2dos...if I had known it existed.</description>
		<content:encoded><![CDATA[<p>I used dos2unix because I just needed a standard line ending before applying CRLF.  Yes, it probably would have made more sense to use unix2dos&#8230;if I had known it existed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chase</title>
		<link>http://blog.eflow.org/archives/130/comment-page-1#comment-300</link>
		<dc:creator>chase</dc:creator>
		<pubDate>Tue, 09 Jun 2009 01:45:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eflow.org/?p=130#comment-300</guid>
		<description>Why did we end up doing dos2unix and then CRLF.... that seems wrong.  Shouldn&#039;t it have been unix2dos and then CRLF or dos2unix and then LF??</description>
		<content:encoded><![CDATA[<p>Why did we end up doing dos2unix and then CRLF&#8230;. that seems wrong.  Shouldn&#8217;t it have been unix2dos and then CRLF or dos2unix and then LF??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The eflow blog &#187; Merge Problems with Inconsistent Newlines in SVN</title>
		<link>http://blog.eflow.org/archives/130/comment-page-1#comment-197</link>
		<dc:creator>The eflow blog &#187; Merge Problems with Inconsistent Newlines in SVN</dc:creator>
		<pubDate>Thu, 18 Dec 2008 19:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eflow.org/?p=130#comment-197</guid>
		<description>[...] the fix_newlines.sh [...]</description>
		<content:encoded><![CDATA[<p>[...] the fix_newlines.sh [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://blog.eflow.org/archives/130/comment-page-1#comment-171</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 03 Nov 2008 17:00:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eflow.org/?p=130#comment-171</guid>
		<description>That is an excellent point, Burke.  And I just forgot to mention my solution for that.  I added the svn:default-eol-style property to the root folder so that all new files get the CRLF property by default.  See &lt;a href=&quot;http://dev.openmrs.org/browser/openmrs/trunk?rev=5893&quot; rel=&quot;nofollow&quot;&gt;http://dev.openmrs.org/browser/openmrs/trunk?rev=5893&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>That is an excellent point, Burke.  And I just forgot to mention my solution for that.  I added the svn:default-eol-style property to the root folder so that all new files get the CRLF property by default.  See <a href="http://dev.openmrs.org/browser/openmrs/trunk?rev=5893" rel="nofollow">http://dev.openmrs.org/browser/openmrs/trunk?rev=5893</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Burke</title>
		<link>http://blog.eflow.org/archives/130/comment-page-1#comment-170</link>
		<dc:creator>Burke</dc:creator>
		<pubDate>Mon, 03 Nov 2008 16:56:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.eflow.org/?p=130#comment-170</guid>
		<description>Do all source files committed to the repository have to have this property set -- i.e., will we have to do this repeatedly over time as new files are added to the repository without the svn:eol-style property set?  If so, is there an alternative (permanent) solution -- e.g., automatically apply this property to all source files via an svn hook?</description>
		<content:encoded><![CDATA[<p>Do all source files committed to the repository have to have this property set &#8212; i.e., will we have to do this repeatedly over time as new files are added to the repository without the svn:eol-style property set?  If so, is there an alternative (permanent) solution &#8212; e.g., automatically apply this property to all source files via an svn hook?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
