<?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: Schedule for Republican work, May-June 2019</title>
	<atom:link href="http://thetarpit.org/2019/tmsr-work-ii/feed" rel="self" type="application/rss+xml" />
	<link>http://thetarpit.org/2019/tmsr-work-ii</link>
	<description>"Now I feel like I know less about what that blog is about than I did before."</description>
	<pubDate>Tue, 14 Apr 2026 23:02:32 +0000</pubDate>
	<generator>http://thetarpit.org</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Common Lisp WWWism summary &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-122</link>
		<dc:creator>Common Lisp WWWism summary &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-122</guid>
		<description>[...] article is part of a series on Common Lisp WWWism, more specifically a summary of what's been discussed so far and some conclusions. Maybe there [...]</description>
		<content:encoded><![CDATA[<p>[...] article is part of a series on Common Lisp WWWism, more specifically a summary of what's been discussed so far and some conclusions. Maybe there [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hunchentoot: acceptor code review &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-108</link>
		<dc:creator>Hunchentoot: acceptor code review &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:27:09 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-108</guid>
		<description>[...] post is part of a series on Common Lisp WWWism, more specifically of ongoing work to understand the web server known as Hunchentoot. Even more [...]</description>
		<content:encoded><![CDATA[<p>[...] post is part of a series on Common Lisp WWWism, more specifically of ongoing work to understand the web server known as Hunchentoot. Even more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hunchentoot: further architectural notes; and usage examples &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-106</link>
		<dc:creator>Hunchentoot: further architectural notes; and usage examples &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-106</guid>
		<description>[...] post is part of a series on Common Lisp WWWism, more specifically a continuation of ongoing work to understand the web server known as Hunchentoot [...]</description>
		<content:encoded><![CDATA[<p>[...] post is part of a series on Common Lisp WWWism, more specifically a continuation of ongoing work to understand the web server known as Hunchentoot [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Notes on Hunchentoot architecture &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-105</link>
		<dc:creator>Notes on Hunchentoot architecture &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-105</guid>
		<description>[...] post is part of a series on Common Lisp WWWism. Before continuing, I heartily recommend a review of prior communications on the [...]</description>
		<content:encoded><![CDATA[<p>[...] post is part of a series on Common Lisp WWWism. Before continuing, I heartily recommend a review of prior communications on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TMSR work: interlude and plan for 2019 M7 &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-103</link>
		<dc:creator>TMSR work: interlude and plan for 2019 M7 &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-103</guid>
		<description>[...] in the forum, as well as my own recent (spectacular) failure to report, let alone deliver, on yet ongoing work, in this post I'm reflecting on what's going on in spykedlands and proposing to take the bull by [...]</description>
		<content:encoded><![CDATA[<p>[...] in the forum, as well as my own recent (spectacular) failure to report, let alone deliver, on yet ongoing work, in this post I'm reflecting on what's going on in spykedlands and proposing to take the bull by [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A review of Hunchentoot's code history &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-102</link>
		<dc:creator>A review of Hunchentoot's code history &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-102</guid>
		<description>[...] post is part of a series on Common Lisp WWWism. Before continuing, please read prior discussions on the [...]</description>
		<content:encoded><![CDATA[<p>[...] post is part of a series on Common Lisp WWWism. Before continuing, please read prior discussions on the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CL-WHO genesis &#171; The Tar Pit</title>
		<link>http://thetarpit.org/2019/tmsr-work-ii#comment-101</link>
		<dc:creator>CL-WHO genesis &#171; The Tar Pit</dc:creator>
		<pubDate>Fri, 11 Oct 2019 12:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://wp.thetarpit.org/2019/tmsr-work-ii#comment-101</guid>
		<description>[...] post is part of a series on Common Lisp WWWism. If you're here, then you've hopefully read prior writings on the matter and understood their [...]</description>
		<content:encoded><![CDATA[<p>[...] post is part of a series on Common Lisp WWWism. If you're here, then you've hopefully read prior writings on the matter and understood their [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
