<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Capi's Corner &#187; eps</title>
	<atom:link href="http://www.dont-panic.cc/capi/tag/eps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dont-panic.cc/capi</link>
	<description>Development, Network, Security, Ideas &#038; Opinions</description>
	<lastBuildDate>Fri, 19 Feb 2010 00:11:10 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>How to force Git to consider a file as binary</title>
		<link>http://www.dont-panic.cc/capi/2009/02/16/how-to-force-git-to-consider-a-file-as-binary/</link>
		<comments>http://www.dont-panic.cc/capi/2009/02/16/how-to-force-git-to-consider-a-file-as-binary/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 21:58:27 +0000</pubDate>
		<dc:creator>Martin Carpella</dc:creator>
				<category><![CDATA[computer]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[eps]]></category>
		<category><![CDATA[git]]></category>
		<category><![CDATA[troubleshooting]]></category>

		<guid isPermaLink="false">http://www.dont-panic.cc/capi/?p=212</guid>
		<description><![CDATA[If you are using Git on Windows and follow my advise on how to get past the problem with the &#8220;suspicious patch lines&#8221;, you might run into problems if you are using Encapsulated PostScript (.eps) files in your repository. PostScript files are almost plain-text files, and if you set core.autocrlf and core.safecrlf, they might cause [...]]]></description>
			<content:encoded><![CDATA[<p>If you are using <a href="http://git-scm.com/">Git</a> on Windows and follow my advise on how to get past <a href="http://www.dont-panic.cc/capi/2007/07/13/git-on-windows-you-have-some-suspicious-patch-lines/">the problem with the &#8220;suspicious patch lines&#8221;</a>, you might run into problems if you are using <a href="http://en.wikipedia.org/wiki/Encapsulated_PostScript">Encapsulated PostScript</a> (.eps) files in your repository.</p>
<p>PostScript files are almost plain-text files, and if you set core.autocrlf and core.safecrlf, they might cause problems with the EPS binary encoded parts, as they might be detected as text-files and therefore remove any CRLF and replace it with single LF, which can mess up the whole image.</p>
<p>To force Git to consider a file binary which it would consider as text-file otherwise, the easiest way is to add a .gitattributes file to the directory containing the file or to any parent directory. In my case, I normally add a .gitattributes file in the root of the repository, containing</p>
<blockquote><p>*.eps -crlf<br />
*.jpg -crlf<br />
*.png -crlf</p></blockquote>
<p>In the file you set attributes to a path (or a pattern), or unset them (with the minus sign).  The crlf attribute is the attribute which tells if a file is affected by the core.autocrlf options. If you unset it, Git won&#8217;t mess with the line endings in the file.</p>
<p>More details can be found on the <a href="http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html">gitattributes man page</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dont-panic.cc/capi/2009/02/16/how-to-force-git-to-consider-a-file-as-binary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
