<?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 for BigSmoke</title>
	<atom:link href="http://blog.bigsmoke.us/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bigsmoke.us</link>
	<description>Smokes your problems, coughs fresh air.</description>
	<lastBuildDate>Thu, 11 Mar 2010 21:43:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Tracking MediaWiki in a Subversion vendor branch by Rowan Rodrik</title>
		<link>http://blog.bigsmoke.us/2009/07/20/svn-vendor-branches#comment-92450</link>
		<dc:creator>Rowan Rodrik</dc:creator>
		<pubDate>Thu, 11 Mar 2010 21:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=672#comment-92450</guid>
		<description>I just extracted this script from my private repo for the Omega Research Wiki and turned it into a separate GitHub project: &lt;a href=&quot;http://github.com/bigsmoke/svn-upgrade-mediawiki&quot; rel=&quot;nofollow&quot;&gt;svn-upgrade-mediawiki&lt;/a&gt;. The reason is simply that I needed to upgrade my hardwood wikis and I don&#039;t want to have to maintain a handful of different versions of the same script.

I had actually used &lt;tt&gt;svn_load_dirs.pl&lt;/tt&gt; directly for these two wikis, so I had to take a few additional steps because my script strips “mediawiki-” part in the extracted dir name from the generated tag name. I upgraded my Dutch hardwood investments wiki like this:

&lt;code lang=&quot;bash&quot;&gt;
svn-upgrade-mediawiki 1.14.0 1.15.2
# There&#039;s a merge failure; let&#039;s find out why
svn list file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki
&lt;/code&gt;
&lt;pre&gt;
1.15.2/
current/
mediawiki-1.12.0/
mediawiki-1.14.0/
&lt;/pre&gt;
&lt;code lang=&quot;bash&quot;&gt;
# Let&#039;s rename these mediawiki-$v tags
vendor_base=file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki
for v in 1.12.0 1.14.0
  do svn mv $vendor_base/mediawiki-$v $vendor_base/$v -m &quot;Renamed mw $v vendor tag.&quot;
done
&lt;/code&gt;

&lt;code lang=&quot;bash&quot;&gt;
# Now, let&#039;s do a manual merge
svn merge file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki/{1.14.0,1.15.2}
&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>I just extracted this script from my private repo for the Omega Research Wiki and turned it into a separate GitHub project: <a href="http://github.com/bigsmoke/svn-upgrade-mediawiki" rel="nofollow">svn-upgrade-mediawiki</a>. The reason is simply that I needed to upgrade my hardwood wikis and I don&#8217;t want to have to maintain a handful of different versions of the same script.</p>
<p>I had actually used <tt>svn_load_dirs.pl</tt> directly for these two wikis, so I had to take a few additional steps because my script strips “mediawiki-” part in the extracted dir name from the generated tag name. I upgraded my Dutch hardwood investments wiki like this:</p>
<p><pre class="bash">svn-upgrade-mediawiki <span style="color: #cc66cc;">1.14</span><span style="color: #cc66cc;">.0</span> <span style="color: #cc66cc;">1.15</span><span style="color: #cc66cc;">.2</span>
<span style="color: #808080; font-style: italic;"># There's a merge failure; let's find out why</span>
svn list file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki</pre></p>
<pre>
1.15.2/
current/
mediawiki-1.12.0/
mediawiki-1.14.0/
</pre>
<p><pre class="bash"><span style="color: #808080; font-style: italic;"># Let's rename these mediawiki-$v tags</span>
<span style="color: #0000ff;">vendor_base=</span>file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki
<span style="color: #b1b100;">for</span> v <span style="color: #b1b100;">in</span> <span style="color: #cc66cc;">1.12</span><span style="color: #cc66cc;">.0</span> <span style="color: #cc66cc;">1.14</span><span style="color: #cc66cc;">.0</span>
  <span style="color: #b1b100;">do</span> svn mv <span style="color: #0000ff;">$vendor_base</span>/mediawiki-<span style="color: #0000ff;">$v</span> <span style="color: #0000ff;">$vendor_base</span>/<span style="color: #0000ff;">$v</span> -m <span style="color: #ff0000;">&quot;Renamed mw $v vendor tag.&quot;</span>
<span style="color: #b1b100;">done</span></pre></p>
<p><pre class="bash"><span style="color: #808080; font-style: italic;"># Now, let's do a manual merge</span>
svn merge file:///var/svn/wiki.hardhout-investeringen.net/vendor/mediawiki/<span style="color: #66cc66;">&#123;</span><span style="color: #cc66cc;">1.14</span><span style="color: #cc66cc;">.0</span>,<span style="color: #cc66cc;">1.15</span><span style="color: #cc66cc;">.2</span><span style="color: #66cc66;">&#125;</span></pre></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Enforcing Drupal URL aliases by Tony Chung</title>
		<link>http://blog.bigsmoke.us/2009/06/10/enforcing-drupal-url-aliases#comment-92099</link>
		<dc:creator>Tony Chung</dc:creator>
		<pubDate>Wed, 24 Feb 2010 22:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=574#comment-92099</guid>
		<description>Very pretty. Now if only Drupal could automatically create the URL aliases for us, like Wordpress. I sometimes wonder if I hack Drupal just for the power and the possibilities? There must be an easy way to use Wordpress and Pods to do the same thing.</description>
		<content:encoded><![CDATA[<p>Very pretty. Now if only Drupal could automatically create the URL aliases for us, like Wordpress. I sometimes wonder if I hack Drupal just for the power and the possibilities? There must be an easy way to use Wordpress and Pods to do the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Learning PC assembly language by Rowan Rodrik</title>
		<link>http://blog.bigsmoke.us/2010/02/18/pc-asm#comment-91966</link>
		<dc:creator>Rowan Rodrik</dc:creator>
		<pubDate>Fri, 19 Feb 2010 13:38:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1278#comment-91966</guid>
		<description>I still need to add the tags to the new design. In my old design, they where displayed in one of the darlings which I killed. I suppose that&#039;s part of the reason why I haven&#039;t added them at the time. :-?

Soon, really soon; I promise!</description>
		<content:encoded><![CDATA[<p>I still need to add the tags to the new design. In my old design, they where displayed in one of the darlings which I killed. I suppose that&#8217;s part of the reason why I haven&#8217;t added them at the time. <img src='http://blog.bigsmoke.us/wp-factory/wp-includes/images/smilies/icon_confused.gif' alt=':-?' class='wp-smiley' /> </p>
<p>Soon, really soon; I promise!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preventing syntax errors with old shell scripts by halfgaar</title>
		<link>http://blog.bigsmoke.us/2010/02/14/preventing-syntax-errors-with-old-shell-scripts#comment-91928</link>
		<dc:creator>halfgaar</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:45:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1257#comment-91928</guid>
		<description>Actually, it was a broken hard disk. I might be interested in that. Things like memory too, perhaps.

So, what machine is it?</description>
		<content:encoded><![CDATA[<p>Actually, it was a broken hard disk. I might be interested in that. Things like memory too, perhaps.</p>
<p>So, what machine is it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Learning PC assembly language by halfgaar</title>
		<link>http://blog.bigsmoke.us/2010/02/18/pc-asm#comment-91927</link>
		<dc:creator>halfgaar</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1278#comment-91927</guid>
		<description>As a sidenote; the tags it has aren&#039;t displayed. And, can&#039;t I tag it as well?</description>
		<content:encoded><![CDATA[<p>As a sidenote; the tags it has aren&#8217;t displayed. And, can&#8217;t I tag it as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Learning PC assembly language by halfgaar</title>
		<link>http://blog.bigsmoke.us/2010/02/18/pc-asm#comment-91926</link>
		<dc:creator>halfgaar</dc:creator>
		<pubDate>Thu, 18 Feb 2010 22:12:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1278#comment-91926</guid>
		<description>I love how you dare to put that image here. And I love how our hosting provider doesn&#039;t mind :)

The &lt;a href=&quot;http://en.wikipedia.org/wiki/Video_Graphics_Array&quot; rel=&quot;nofollow&quot;&gt;Video Graphics Array (VGA)&lt;/a&gt; page on wikipedia has the palette.

&lt;a href=&quot;http://lrs.uni-passau.de/support/doc/interrupt-57/INT.HTM&quot; rel=&quot;nofollow&quot;&gt;Interrupt API&lt;/a&gt;. I don&#039;t know if we used this, but it&#039;s a very good one I found.</description>
		<content:encoded><![CDATA[<p>I love how you dare to put that image here. And I love how our hosting provider doesn&#8217;t mind <img src='http://blog.bigsmoke.us/wp-factory/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>The <a href="http://en.wikipedia.org/wiki/Video_Graphics_Array" rel="nofollow">Video Graphics Array (VGA)</a> page on wikipedia has the palette.</p>
<p><a href="http://lrs.uni-passau.de/support/doc/interrupt-57/INT.HTM" rel="nofollow">Interrupt API</a>. I don&#8217;t know if we used this, but it&#8217;s a very good one I found.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preventing syntax errors with old shell scripts by Rowan Rodrik</title>
		<link>http://blog.bigsmoke.us/2010/02/14/preventing-syntax-errors-with-old-shell-scripts#comment-91921</link>
		<dc:creator>Rowan Rodrik</dc:creator>
		<pubDate>Thu, 18 Feb 2010 17:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1257#comment-91921</guid>
		<description>Well, I thought I heard you mention that one of your gaming machines was broken or at least had a broken screen.</description>
		<content:encoded><![CDATA[<p>Well, I thought I heard you mention that one of your gaming machines was broken or at least had a broken screen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Learning PC assembly language by Rowan Rodrik</title>
		<link>http://blog.bigsmoke.us/2010/02/18/pc-asm#comment-91918</link>
		<dc:creator>Rowan Rodrik</dc:creator>
		<pubDate>Thu, 18 Feb 2010 15:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1278#comment-91918</guid>
		<description>From the Wikipedia &lt;a href=&quot;http://en.wikipedia.org/wiki/Category:BIOS&quot; rel=&quot;nofollow&quot;&gt;BIOS&lt;/a&gt; category: &lt;a href=&quot;http://en.wikipedia.org/wiki/BIOS_interrupt_call&quot; rel=&quot;nofollow&quot;&gt;&lt;cite&gt;BIOS interrupt call&lt;/cite&gt;&lt;/a&gt; and &lt;a href=&quot;http://en.wikipedia.org/wiki/INT_10&quot; rel=&quot;nofollow&quot;&gt;&lt;cite&gt;INT 10&lt;/cite&gt;&lt;/a&gt;
Also: &lt;a href=&quot;http://en.wikipedia.org/wiki/BIOS_color_attributes&quot; rel=&quot;nofollow&quot;&gt;&lt;cite&gt;BIOS color attributes&lt;/cite&gt;&lt;/a&gt;
And for the next version of the program: &lt;a href=&quot;http://en.wikipedia.org/wiki/VESA_BIOS_Extensions&quot; rel=&quot;nofollow&quot;&gt;&lt;cite&gt;VESA BIOS Extensions&lt;/cite&gt;&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>From the Wikipedia <a href="http://en.wikipedia.org/wiki/Category:BIOS" rel="nofollow">BIOS</a> category: <a href="http://en.wikipedia.org/wiki/BIOS_interrupt_call" rel="nofollow"><cite>BIOS interrupt call</cite></a> and <a href="http://en.wikipedia.org/wiki/INT_10" rel="nofollow"><cite>INT 10</cite></a><br />
Also: <a href="http://en.wikipedia.org/wiki/BIOS_color_attributes" rel="nofollow"><cite>BIOS color attributes</cite></a><br />
And for the next version of the program: <a href="http://en.wikipedia.org/wiki/VESA_BIOS_Extensions" rel="nofollow"><cite>VESA BIOS Extensions</cite></a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blog competition by Rowan Rodrik</title>
		<link>http://blog.bigsmoke.us/2010/02/15/blog-competition#comment-91897</link>
		<dc:creator>Rowan Rodrik</dc:creator>
		<pubDate>Wed, 17 Feb 2010 22:27:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1265#comment-91897</guid>
		<description>Shit! You caught me cheating!</description>
		<content:encoded><![CDATA[<p>Shit! You caught me cheating!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Preventing syntax errors with old shell scripts by halfgaar</title>
		<link>http://blog.bigsmoke.us/2010/02/14/preventing-syntax-errors-with-old-shell-scripts#comment-91886</link>
		<dc:creator>halfgaar</dc:creator>
		<pubDate>Wed, 17 Feb 2010 17:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=1257#comment-91886</guid>
		<description>I don&#039;t really see the relvance of UT and a machine, but can you give me some kind of indication about the specs? GHz? Or is it that P3 500?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t really see the relvance of UT and a machine, but can you give me some kind of indication about the specs? GHz? Or is it that P3 500?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
