<?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"
	>
<channel>
	<title>Comments on: Difficult gitk Graphs</title>
	<atom:link href="http://www.spearce.org/2007/07/difficult-gitk-graphs.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.spearce.org/2007/07/difficult-gitk-graphs.html</link>
	<description>The lonely musings of a loosely connected software developer.</description>
	<pubDate>Tue, 06 Jan 2009 10:26:27 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Sverre Rabbelier</title>
		<link>http://www.spearce.org/2007/07/difficult-gitk-graphs.html#comment-91780</link>
		<dc:creator>Sverre Rabbelier</dc:creator>
		<pubDate>Fri, 18 Jul 2008 19:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.spearce.org/2007/07/difficult-gitk-graphs.html#comment-91780</guid>
		<description>I'm not sure if this is hilarious or depressing, maybe a little bit of both :P. What can we do when a repository has such a insane number of commits though? Maybe what could be done is that instead of showing every branch that got merged, only show the requested branches. E.g., in the case of 'gitk master maint' only show the development of master and maint, and show merged-in branches as one point in the graph, instead of as a full line with all the commits made on that branch. This reduces the amount of information you have (you lose the information on what exactly was merged in),  but with such a huge amount of data, gitk is hardly useful anymore anyway. I know that I would love an option to trim merged-in branches when looking at git.git!</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if this is hilarious or depressing, maybe a little bit of both :P. What can we do when a repository has such a insane number of commits though? Maybe what could be done is that instead of showing every branch that got merged, only show the requested branches. E.g., in the case of &#8216;gitk master maint&#8217; only show the development of master and maint, and show merged-in branches as one point in the graph, instead of as a full line with all the commits made on that branch. This reduces the amount of information you have (you lose the information on what exactly was merged in),  but with such a huge amount of data, gitk is hardly useful anymore anyway. I know that I would love an option to trim merged-in branches when looking at git.git!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael J. Cohen</title>
		<link>http://www.spearce.org/2007/07/difficult-gitk-graphs.html#comment-60620</link>
		<dc:creator>Michael J. Cohen</dc:creator>
		<pubDate>Wed, 07 Nov 2007 23:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.spearce.org/2007/07/difficult-gitk-graphs.html#comment-60620</guid>
		<description>This is hilarious.</description>
		<content:encoded><![CDATA[<p>This is hilarious.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
