<?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>Kommentare zu: Upcoming improvements of the Mercurial Bookmarks extension</title>
	<atom:link href="http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/feed/" rel="self" type="application/rss+xml" />
	<link>http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/</link>
	<description>Im Wendekreis des Elbfisches</description>
	<lastBuildDate>Sat, 27 Mar 2010 21:58:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Von: Bastian</title>
		<link>http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/comment-page-1/#comment-3010</link>
		<dc:creator>Bastian</dc:creator>
		<pubDate>Sat, 17 Jan 2009 16:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://doetsch.info/?p=147#comment-3010</guid>
		<description>So I wonder, who&#039;ll tackle the wire protocol - it would open up a lot of possibilities for extensions if metadata could be synched.</description>
		<content:encoded><![CDATA[<p>So I wonder, who&#8217;ll tackle the wire protocol &#8211; it would open up a lot of possibilities for extensions if metadata could be synched.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: dsp</title>
		<link>http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/comment-page-1/#comment-3001</link>
		<dc:creator>dsp</dc:creator>
		<pubDate>Fri, 02 Jan 2009 13:56:49 +0000</pubDate>
		<guid isPermaLink="false">http://doetsch.info/?p=147#comment-3001</guid>
		<description>well we actually decided that we want to use some more generic option do allow pushing/pulling heads, so the non-bookmarked option was backed out.
What we kept was the including of bookmark names in log, and the track.current option, so those will be in 1.2.</description>
		<content:encoded><![CDATA[<p>well we actually decided that we want to use some more generic option do allow pushing/pulling heads, so the non-bookmarked option was backed out.<br />
What we kept was the including of bookmark names in log, and the track.current option, so those will be in 1.2.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Bastian Doetsch</title>
		<link>http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/comment-page-1/#comment-3000</link>
		<dc:creator>Bastian Doetsch</dc:creator>
		<pubDate>Fri, 02 Jan 2009 08:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://doetsch.info/?p=147#comment-3000</guid>
		<description>Too bad - I really would have appreciated it, as this is a major point hindering adoption. So what kind of solution did you guys decide on? And will you implement it or will somebody else do so?</description>
		<content:encoded><![CDATA[<p>Too bad &#8211; I really would have appreciated it, as this is a major point hindering adoption. So what kind of solution did you guys decide on? And will you implement it or will somebody else do so?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: dsp</title>
		<link>http://doetsch.info/2008/12/07/upcoming-improvements-of-the-mercurial-bookmarks-extension/comment-page-1/#comment-2999</link>
		<dc:creator>dsp</dc:creator>
		<pubDate>Fri, 02 Jan 2009 00:25:24 +0000</pubDate>
		<guid isPermaLink="false">http://doetsch.info/?p=147#comment-2999</guid>
		<description>I&#039;m so sorry that those changesets had to be backed-out because of some discussion in IRC . We came to the conclusion that this is no the right way to fix those things :/</description>
		<content:encoded><![CDATA[<p>I&#8217;m so sorry that those changesets had to be backed-out because of some discussion in IRC . We came to the conclusion that this is no the right way to fix those things :/</p>
]]></content:encoded>
	</item>
</channel>
</rss>

