<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cvs on Pesches Schlauch</title>
    <link>https://pesche.schlau.ch/tags/cvs/</link>
    <description>Recent content in Cvs on Pesches Schlauch</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 07 Feb 2005 10:07:04 +0100</lastBuildDate>
    <atom:link href="https://pesche.schlau.ch/tags/cvs/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CVS with AppleSingle files</title>
      <link>https://pesche.schlau.ch/2005/02/07/cvs-with-applesingle-files/</link>
      <pubDate>Mon, 07 Feb 2005 10:07:04 +0100</pubDate>
      <guid>https://pesche.schlau.ch/2005/02/07/cvs-with-applesingle-files/</guid>
      <description>&lt;p&gt;Longtime Apple developers probably know this intuitively, but I needed some time to figure it out: When CVS-ing files with a resource fork, you &lt;strong&gt;must not&lt;/strong&gt; use the &lt;code&gt;/usr/bin/cvs&lt;/code&gt; that ships with OS X!&lt;/p&gt;&#xA;&lt;p&gt;Because Apple used to separate data and metadata, most files in the pre OS X era had a data fork and a resource fork, but for the user this was transparent; the user just manipulated one file. Tools without this &amp;quot;Classic&amp;quot; background know nothing of the resource fork. Files without data fork appear in the Terminal to have 0 bytes.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
