<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>duke3d_hrp &#x2013; /highres/textures/0153_g.png</title><description>WebSVN RSS feed &#x2013; duke3d_hrp</description><lastBuildDate>Fri, 31 Jul 2026 21:29:22 +0000</lastBuildDate><generator>WebSVN 2.8.9-DEV</generator><language>en</language><link>https://svn.eduke32.com/websvn/log.php?repname=duke3d_hrp&amp;path=%2Fhighres%2Ftextures%2F0153_g.png&amp;max=40&amp;peg=606</link><atom:link href="https://svn.eduke32.com/websvn/rss.php?path=%2Fhighres%2Ftextures%2F0153_g.png&amp;peg=606&amp;repname=duke3d_hrp" rel="self" type="application/rss+xml" />
<item><pubDate>Fri, 20 Jul 2012 22:18:52 +0000</pubDate><dc:creator>leod</dc:creator><title>Rev 396 – Polymost glowmaps added;  duke3d.def: remove irritating comment.  I&apos;m ...</title><description>&lt;div&gt;&lt;strong&gt;leod – 4 file(s) modified&lt;/strong&gt;&lt;br/&gt;Polymost glowmaps added;  duke3d.def: remove irritating comment.&lt;br /&gt;
&lt;br /&gt;
I&apos;m not really happy with this solution but up to now only four files are affected by this rare Polymer/Polymost conflict. And so far I think it&apos;s better for maintenance not to introduce a textures_polymost folder.&lt;br /&gt;
&lt;br /&gt;
duke3d.def: This is definetely not the place to split the DEF path between Polymer and Polymost.&lt;/div&gt;~ /duke3d.def&lt;br /&gt;+ /highres/textures/0152_g.png&lt;br /&gt;+ /highres/textures/0153_g.png&lt;br /&gt;~ /highres/textures_polymost.def&lt;br /&gt;</description><link>https://svn.eduke32.com/websvn/revision.php?repname=duke3d_hrp&amp;path=%2Fhighres%2Ftextures%2F0153_g.png&amp;rev=396&amp;peg=606</link><guid>https://svn.eduke32.com/websvn/revision.php?repname=duke3d_hrp&amp;path=%2Fhighres%2Ftextures%2F0153_g.png&amp;rev=396&amp;peg=606</guid></item>
</channel></rss>