<?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: Mercurial: The Definitive Guide</title>
	<atom:link href="http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/</link>
	<description>Bryan O&#039;Sullivan&#039;s blog</description>
	<lastBuildDate>Wed, 08 Feb 2012 06:41:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nicolas</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-249439</link>
		<dc:creator>Nicolas</dc:creator>
		<pubDate>Tue, 10 Nov 2009 05:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-249439</guid>
		<description>I&#039;m *so* borrowing your comment system! Thanks for giving the source!</description>
		<content:encoded><![CDATA[<p>I&#8217;m *so* borrowing your comment system! Thanks for giving the source!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lukas</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-232165</link>
		<dc:creator>Lukas</dc:creator>
		<pubDate>Tue, 02 Jun 2009 12:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-232165</guid>
		<description>Thanks a lot for that guide. It helps me understanding the ideas behind mercurial.</description>
		<content:encoded><![CDATA[<p>Thanks a lot for that guide. It helps me understanding the ideas behind mercurial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan O'Sullivan</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-228069</link>
		<dc:creator>Bryan O'Sullivan</dc:creator>
		<pubDate>Tue, 05 May 2009 06:19:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-228069</guid>
		<description>Mark, what happened with some of the infelicities was that Mercurial itself changed, and it had been a while since I updated the text of the book. Thanks for spotting them.

I&#039;ve tidied up that example to be a little more obvious.</description>
		<content:encoded><![CDATA[<p>Mark, what happened with some of the infelicities was that Mercurial itself changed, and it had been a while since I updated the text of the book. Thanks for spotting them.</p>
<p>I&#8217;ve tidied up that example to be a little more obvious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Blakeney</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-228067</link>
		<dc:creator>Mark Blakeney</dc:creator>
		<pubDate>Tue, 05 May 2009 06:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-228067</guid>
		<description>There&#039;s a shell comment &quot;The file new-hello.c is lightly edited&quot;. Sorry, that sentence did/does not make sense. More to the point however is that the file is copied from the parent directory which is not a repo area. Where did that source file magically come from? I struck this confusing point and the later merge abort example and it just seemed to me the tutorial examples had got out of sync with the words in some kind of documentation build error.

I&#039;m here because one of the significant advantages stated by Google Code when they recently choose mercurial over git was its documentation, in particular they quoted your book (see http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html). So, seeing these simple errors in an early chapter, leads me to conclude they must be very recently introduced, possibly by this new django implementation. Surely these errors have not always existed?

Thanks for this great resource however and thanks for commenting back to me here. Have you looked at why the comments don&#039;t work reliably on the book site?</description>
		<content:encoded><![CDATA[<p>There&#8217;s a shell comment &#8220;The file new-hello.c is lightly edited&#8221;. Sorry, that sentence did/does not make sense. More to the point however is that the file is copied from the parent directory which is not a repo area. Where did that source file magically come from? I struck this confusing point and the later merge abort example and it just seemed to me the tutorial examples had got out of sync with the words in some kind of documentation build error.</p>
<p>I&#8217;m here because one of the significant advantages stated by Google Code when they recently choose mercurial over git was its documentation, in particular they quoted your book (see <a href="http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html" rel="nofollow">http://google-code-updates.blogspot.com/2009/04/mercurial-support-for-project-hosting.html</a>). So, seeing these simple errors in an early chapter, leads me to conclude they must be very recently introduced, possibly by this new django implementation. Surely these errors have not always existed?</p>
<p>Thanks for this great resource however and thanks for commenting back to me here. Have you looked at why the comments don&#8217;t work reliably on the book site?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan O'Sullivan</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-228037</link>
		<dc:creator>Bryan O'Sullivan</dc:creator>
		<pubDate>Tue, 05 May 2009 03:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-228037</guid>
		<description>Mark, there&#039;s a comment describing what new-hello.c is in the actual shell example. Is that not clear enough? If so, I&#039;ll find some other way to flag it.</description>
		<content:encoded><![CDATA[<p>Mark, there&#8217;s a comment describing what new-hello.c is in the actual shell example. Is that not clear enough? If so, I&#8217;ll find some other way to flag it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Blakeney</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-228016</link>
		<dc:creator>Mark Blakeney</dc:creator>
		<pubDate>Tue, 05 May 2009 01:37:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-228016</guid>
		<description>Hi Bryan, I see today that you have fixed some of the errors in chapter 2 I refer to above. There is at least one other blatant error but I can&#039;t comment on the site because the comment system now just hangs for me.

First error on chapter 2 page occurs in the very first figure on the page. In the line &quot;cp ../new-hello.c hello.c&quot; where does new-hello.c come from? It was not created in the previous chapter. Further down you say you have fixed the merge abort example and you say to &quot;notice that it has both of our former heads as its parents&quot; but the bottom of the figure has merely been cut off so the result can not be seen at all.</description>
		<content:encoded><![CDATA[<p>Hi Bryan, I see today that you have fixed some of the errors in chapter 2 I refer to above. There is at least one other blatant error but I can&#8217;t comment on the site because the comment system now just hangs for me.</p>
<p>First error on chapter 2 page occurs in the very first figure on the page. In the line &#8220;cp ../new-hello.c hello.c&#8221; where does new-hello.c come from? It was not created in the previous chapter. Further down you say you have fixed the merge abort example and you say to &#8220;notice that it has both of our former heads as its parents&#8221; but the bottom of the figure has merely been cut off so the result can not be seen at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Blakeney</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-227417</link>
		<dc:creator>Mark Blakeney</dc:creator>
		<pubDate>Sat, 02 May 2009 03:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-227417</guid>
		<description>Bryan, I think something is badly broken in the new book. I&#039;m a mercurial newbie and tried to follow the tutorial but there are too many errors. See chapter 2 where I left one comment (along with other people) describing some blatant mismatches between the figures and the words. Something is also wrong with the comment system as after my first comment it now always just hangs when I try to enter another comment. So note there are errors from the 1st figure on in chapter 2 but I could not comment there about them.</description>
		<content:encoded><![CDATA[<p>Bryan, I think something is badly broken in the new book. I&#8217;m a mercurial newbie and tried to follow the tutorial but there are too many errors. See chapter 2 where I left one comment (along with other people) describing some blatant mismatches between the figures and the words. Something is also wrong with the comment system as after my first comment it now always just hangs when I try to enter another comment. So note there are errors from the 1st figure on in chapter 2 but I could not comment there about them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paddy3118</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-226155</link>
		<dc:creator>Paddy3118</dc:creator>
		<pubDate>Sun, 26 Apr 2009 10:16:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-226155</guid>
		<description>Hi,
I&#039;ve just started reading the online edition, and would just say that it would be nice if the comment indicator was a different pale colour to indicate when people had actually made some comments on a paragraph.

- Paddy.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I&#8217;ve just started reading the online edition, and would just say that it would be nice if the comment indicator was a different pale colour to indicate when people had actually made some comments on a paragraph.</p>
<p>- Paddy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Vandervort</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-219843</link>
		<dc:creator>John Vandervort</dc:creator>
		<pubDate>Mon, 30 Mar 2009 22:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-219843</guid>
		<description>Great Book!  Congrats.  It was very helpful.
Are the links in the rss comment feeds supposed to be going to example.com?</description>
		<content:encoded><![CDATA[<p>Great Book!  Congrats.  It was very helpful.<br />
Are the links in the rss comment feeds supposed to be going to example.com?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arne Babenhauserheide</title>
		<link>http://www.serpentine.com/blog/2009/03/27/mercurial-the-definitive-guide/comment-page-1/#comment-219338</link>
		<dc:creator>Arne Babenhauserheide</dc:creator>
		<pubDate>Sat, 28 Mar 2009 10:12:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.serpentine.com/blog/?p=343#comment-219338</guid>
		<description>I already know your book, so what gripped me first wasn&#039;t it content, but the comment system. 

I just love that! 

I searched for _exactly this_ for years (for shadowtalk...), but everything I found had flaws which made it unusable for me. 

What&#039;s the license of your comment system? (GPL compatible?)</description>
		<content:encoded><![CDATA[<p>I already know your book, so what gripped me first wasn&#8217;t it content, but the comment system. </p>
<p>I just love that! </p>
<p>I searched for _exactly this_ for years (for shadowtalk&#8230;), but everything I found had flaws which made it unusable for me. </p>
<p>What&#8217;s the license of your comment system? (GPL compatible?)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

