<?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: v0.7 Release &#8211; Repeating Bug with Merge Changesets</title>
	<atom:link href="http://blog.sidkalra.com/2009/03/v07-release-repeating-bug-with-merge-changesets/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sidkalra.com/2009/03/v07-release-repeating-bug-with-merge-changesets/</link>
	<description></description>
	<lastBuildDate>Sun, 03 Jul 2011 03:10:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Justin Wood (Callek)</title>
		<link>http://blog.sidkalra.com/2009/03/v07-release-repeating-bug-with-merge-changesets/#comment-91</link>
		<dc:creator>Justin Wood (Callek)</dc:creator>
		<pubDate>Mon, 16 Mar 2009 00:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sidkalra.com/?p=402#comment-91</guid>
		<description>Without staring at code, it sounds like you should really be only showing what changesets are _pushed_. IE. the merge is also a changeset.

If people need to see what the merge&#039;s parents are they can click through to see the merge.

So it sounds like what happens here is that you are displaying the merge&#039;s parent(s) rather than the the push&#039;s themselves.

Realize that a merge will always have two parents, one of which is *very likely* to have been there from a previous push.

In future I may have time to stare at this code with you and work out a solution if you don&#039;t beat me to it.</description>
		<content:encoded><![CDATA[<p>Without staring at code, it sounds like you should really be only showing what changesets are _pushed_. IE. the merge is also a changeset.</p>
<p>If people need to see what the merge&#8217;s parents are they can click through to see the merge.</p>
<p>So it sounds like what happens here is that you are displaying the merge&#8217;s parent(s) rather than the the push&#8217;s themselves.</p>
<p>Realize that a merge will always have two parents, one of which is *very likely* to have been there from a previous push.</p>
<p>In future I may have time to stare at this code with you and work out a solution if you don&#8217;t beat me to it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

