<?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: The right way to cvsup	</title>
	<atom:link href="https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Thu, 08 Apr 2004 03:29:53 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Justin C. Sherrill		</title>
		<link>https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/comment-page-1/#comment-187</link>

		<dc:creator><![CDATA[Justin C. Sherrill]]></dc:creator>
		<pubDate>Thu, 08 Apr 2004 03:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=337#comment-187</guid>

					<description><![CDATA[If I recall correctly, specifically removing /usr/includes/ was for folks upgrading from FreeBSD - this would get rid of header files from FreeBSD that would otherwise stick around, untouched.
]]></description>
			<content:encoded><![CDATA[<p>If I recall correctly, specifically removing /usr/includes/ was for folks upgrading from FreeBSD &#8211; this would get rid of header files from FreeBSD that would otherwise stick around, untouched.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael		</title>
		<link>https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/comment-page-1/#comment-186</link>

		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Wed, 07 Apr 2004 23:42:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=337#comment-186</guid>

					<description><![CDATA[Joerg, thanks for your speedy reply! You DragonFly folks are doing a fantastic job, and I can&#039;t wait for the first release.]]></description>
			<content:encoded><![CDATA[<p>Joerg, thanks for your speedy reply! You DragonFly folks are doing a fantastic job, and I can&#8217;t wait for the first release.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joerg Sonnenberger		</title>
		<link>https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/comment-page-1/#comment-185</link>

		<dc:creator><![CDATA[Joerg Sonnenberger]]></dc:creator>
		<pubDate>Wed, 07 Apr 2004 13:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=337#comment-185</guid>

					<description><![CDATA[Updating /usr/include is a part of buildworld, you only need to do that if you want partial updates.]]></description>
			<content:encoded><![CDATA[<p>Updating /usr/include is a part of buildworld, you only need to do that if you want partial updates.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael		</title>
		<link>https://www.dragonflydigest.com/2004/04/06/the-right-way-to-cvsup/comment-page-1/#comment-184</link>

		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Wed, 07 Apr 2004 03:53:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=337#comment-184</guid>

					<description><![CDATA[Does the new build infrastructure take care of everything in /usr/include, or do we still need to remove, and rebuild that directory and then do a &#039;make includes&#039; from /usr/src?

It&#039;s burned me before, so I&#039;d really like to know soon, thanks! :)]]></description>
			<content:encoded><![CDATA[<p>Does the new build infrastructure take care of everything in /usr/include, or do we still need to remove, and rebuild that directory and then do a &#8216;make includes&#8217; from /usr/src?</p>
<p>It&#8217;s burned me before, so I&#8217;d really like to know soon, thanks! :)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
