<?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: Unixy system benchmarks	</title>
	<atom:link href="https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<lastBuildDate>Sat, 10 Apr 2004 08:03:13 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>
	<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/comment-page-1/#comment-196</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Sat, 10 Apr 2004 08:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=339#comment-196</guid>

					<description><![CDATA[Yes, though that&#039;s probably the worst of both worlds as far as compactness is concerned.  (CVS doesn&#039;t quite let you roll around like that, so I suppose it doesn&#039;t really matter, does it?  Unless someone wants to hack on an automatic changelog facility, where the changelog conveniently resides in CVS and rolls over per-tagging -- or one file just records the &#039;last change&#039; touch and gets versioned?  Probably not much fun for diminishing returns...)
]]></description>
			<content:encoded><![CDATA[<p>Yes, though that&#8217;s probably the worst of both worlds as far as compactness is concerned.  (CVS doesn&#8217;t quite let you roll around like that, so I suppose it doesn&#8217;t really matter, does it?  Unless someone wants to hack on an automatic changelog facility, where the changelog conveniently resides in CVS and rolls over per-tagging &#8212; or one file just records the &#8216;last change&#8217; touch and gets versioned?  Probably not much fun for diminishing returns&#8230;)</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Claes "clacke" Wallin		</title>
		<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/comment-page-1/#comment-195</link>

		<dc:creator><![CDATA[Claes "clacke" Wallin]]></dc:creator>
		<pubDate>Fri, 09 Apr 2004 09:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=339#comment-195</guid>

					<description><![CDATA[You mean something like a named/bind serial number? YYMMDD01, YYMMDD02 etc.]]></description>
			<content:encoded><![CDATA[<p>You mean something like a named/bind serial number? YYMMDD01, YYMMDD02 etc.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/comment-page-1/#comment-194</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Fri, 09 Apr 2004 01:13:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=339#comment-194</guid>

					<description><![CDATA[Works for me, and/or if there&#039;s a way to extract a CVS version off something that always increments with each &#039;touch&#039; to the repository, that&#039;d make for even better forensics.]]></description>
			<content:encoded><![CDATA[<p>Works for me, and/or if there&#8217;s a way to extract a CVS version off something that always increments with each &#8216;touch&#8217; to the repository, that&#8217;d make for even better forensics.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Claes Wallin		</title>
		<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/comment-page-1/#comment-193</link>

		<dc:creator><![CDATA[Claes Wallin]]></dc:creator>
		<pubDate>Thu, 08 Apr 2004 10:52:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=339#comment-193</guid>

					<description><![CDATA[FreeBSD-5-040407 sound reasonable, doesn&#039;t it? (ISO date, YYMMDD) That&#039;s the way most people note their CVS versions in e.g. Debian packages not based on released tarballs.]]></description>
			<content:encoded><![CDATA[<p>FreeBSD-5-040407 sound reasonable, doesn&#8217;t it? (ISO date, YYMMDD) That&#8217;s the way most people note their CVS versions in e.g. Debian packages not based on released tarballs.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joe "Floid" Kanowitz		</title>
		<link>https://www.dragonflydigest.com/2004/04/07/unixy-system-benchmarks/comment-page-1/#comment-192</link>

		<dc:creator><![CDATA[Joe "Floid" Kanowitz]]></dc:creator>
		<pubDate>Thu, 08 Apr 2004 05:41:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=339#comment-192</guid>

					<description><![CDATA[Mm, benchmarks!

I&#039;m still reading, but it brings to mind a &#039;usability&#039; annoyance in the BSD versioning system; thankfully, &quot;April 7th, 2004&quot; is specified at the bottom, but elsewise, where Linux gets defined odd-numbered releases, at least 3 out of 4 BSDs get &quot;-CURRENT.&quot;  Not a big deal... until you&#039;re searching around and land on a page of indeterminate date.

Nothing wrong with the development model, but anyone have ideas for a notation better or more compact than &quot;-CURRENT as of DD/MM/YY,&quot; which we all know we should write, but seldom do?  (Of course, that&#039;s date-format chauvinist, but as long as there&#039;d be a &quot;standard&quot;...)]]></description>
			<content:encoded><![CDATA[<p>Mm, benchmarks!</p>
<p>I&#8217;m still reading, but it brings to mind a &#8216;usability&#8217; annoyance in the BSD versioning system; thankfully, &#8220;April 7th, 2004&#8221; is specified at the bottom, but elsewise, where Linux gets defined odd-numbered releases, at least 3 out of 4 BSDs get &#8220;-CURRENT.&#8221;  Not a big deal&#8230; until you&#8217;re searching around and land on a page of indeterminate date.</p>
<p>Nothing wrong with the development model, but anyone have ideas for a notation better or more compact than &#8220;-CURRENT as of DD/MM/YY,&#8221; which we all know we should write, but seldom do?  (Of course, that&#8217;s date-format chauvinist, but as long as there&#8217;d be a &#8220;standard&#8221;&#8230;)</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
