<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Patch-Tag Extends Free Trial, and other developments</title>
	<atom:link href="http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/</link>
	<description>give your code a home</description>
	<lastBuildDate>Fri, 13 Jul 2012 17:30:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Sergey</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-42</link>
		<dc:creator><![CDATA[Sergey]]></dc:creator>
		<pubDate>Fri, 12 Jun 2009 14:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-42</guid>
		<description><![CDATA[Thank you! It&#039;s better than nothing but still not perfect. Some remarks:

1) List of commits:

I often get 502 Proxy Error and the page loads slowly (http://patch-tag.com/r/happstack/snapshots/all/history)

Hashes are really long. Initial part of the hash duplicates the date. Probably it makes sense to visualize only the ending, like ‘...8fe174e57’ in the web UI. 

Layout of the list of commits is less readable than on github or on bitbucket. There, hashes stay separately on the right and the list of updated files is shown only on the page with commit details. (http://github.com/ghc-hq/ghc/commits/master). But I think this will be polished in the future.

2) Commit page:

Striking out deleted text is not really a good idea: it is not clearly visible if the line strikes over the space or over the dash/minus sign. Better change background colour.

Browsing for changes through the whole big file is not very convenient. Diffs/patches are easier to read.

wdiffs are even better (github and bitbucket do it, really nice).

Line numbers may help in certain situations.]]></description>
		<content:encoded><![CDATA[<p>Thank you! It&#8217;s better than nothing but still not perfect. Some remarks:</p>
<p>1) List of commits:</p>
<p>I often get 502 Proxy Error and the page loads slowly (<a href="http://patch-tag.com/r/happstack/snapshots/all/history" rel="nofollow">http://patch-tag.com/r/happstack/snapshots/all/history</a>)</p>
<p>Hashes are really long. Initial part of the hash duplicates the date. Probably it makes sense to visualize only the ending, like ‘&#8230;8fe174e57’ in the web UI. </p>
<p>Layout of the list of commits is less readable than on github or on bitbucket. There, hashes stay separately on the right and the list of updated files is shown only on the page with commit details. (<a href="http://github.com/ghc-hq/ghc/commits/master" rel="nofollow">http://github.com/ghc-hq/ghc/commits/master</a>). But I think this will be polished in the future.</p>
<p>2) Commit page:</p>
<p>Striking out deleted text is not really a good idea: it is not clearly visible if the line strikes over the space or over the dash/minus sign. Better change background colour.</p>
<p>Browsing for changes through the whole big file is not very convenient. Diffs/patches are easier to read.</p>
<p>wdiffs are even better (github and bitbucket do it, really nice).</p>
<p>Line numbers may help in certain situations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Hartman</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-37</link>
		<dc:creator><![CDATA[Thomas Hartman]]></dc:creator>
		<pubDate>Sat, 23 May 2009 18:22:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-37</guid>
		<description><![CDATA[OK, pushed!

What do you think of the new diff functionality?

You can click one of the &quot;hash&quot; type links at, eg

http://patch-tag.com/r/happstack/snapshots/all/history

to see it in action.]]></description>
		<content:encoded><![CDATA[<p>OK, pushed!</p>
<p>What do you think of the new diff functionality?</p>
<p>You can click one of the &#8220;hash&#8221; type links at, eg</p>
<p><a href="http://patch-tag.com/r/happstack/snapshots/all/history" rel="nofollow">http://patch-tag.com/r/happstack/snapshots/all/history</a></p>
<p>to see it in action.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Hartman</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-36</link>
		<dc:creator><![CDATA[Thomas Hartman]]></dc:creator>
		<pubDate>Tue, 19 May 2009 21:52:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-36</guid>
		<description><![CDATA[Yeah, you&#039;re right.

Just did some work on this. Testing, and will push something soon.]]></description>
		<content:encoded><![CDATA[<p>Yeah, you&#8217;re right.</p>
<p>Just did some work on this. Testing, and will push something soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Elder</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-35</link>
		<dc:creator><![CDATA[Matthew Elder]]></dc:creator>
		<pubDate>Tue, 19 May 2009 16:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-35</guid>
		<description><![CDATA[We do have file diffs (if you click on file history in the upper right-hand corner). But yes, we do need patch diffs, we will get this addressed asap.]]></description>
		<content:encoded><![CDATA[<p>We do have file diffs (if you click on file history in the upper right-hand corner). But yes, we do need patch diffs, we will get this addressed asap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mornfall</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-34</link>
		<dc:creator><![CDATA[mornfall]]></dc:creator>
		<pubDate>Tue, 19 May 2009 13:52:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-34</guid>
		<description><![CDATA[Dunno, so far the move away from gitit looks like a regression to me, in term of features (eg. the diffs already mentioned). Hopefully, that gets addressed in the future...]]></description>
		<content:encoded><![CDATA[<p>Dunno, so far the move away from gitit looks like a regression to me, in term of features (eg. the diffs already mentioned). Hopefully, that gets addressed in the future&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergey</title>
		<link>http://blog.patch-tag.com/2009/05/12/patch-tag-extends-free-trial-and-other-developments/#comment-33</link>
		<dc:creator><![CDATA[Sergey]]></dc:creator>
		<pubDate>Fri, 15 May 2009 09:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.patch-tag.com/?p=143#comment-33</guid>
		<description><![CDATA[Hi, Thomas!

I like Patch-Tag. Just two wishes:

1. Add a link to feature requests/bug tracking of the project somewhere (I mean patch-tag). For example, you can add a UserVoice (http://uservoice.com/) widget quickly.

2. It would be nice to be able to see highlighted patches (diffs) when browsing history. Now it&#039;s impossible to see what patch does what.]]></description>
		<content:encoded><![CDATA[<p>Hi, Thomas!</p>
<p>I like Patch-Tag. Just two wishes:</p>
<p>1. Add a link to feature requests/bug tracking of the project somewhere (I mean patch-tag). For example, you can add a UserVoice (<a href="http://uservoice.com/" rel="nofollow">http://uservoice.com/</a>) widget quickly.</p>
<p>2. It would be nice to be able to see highlighted patches (diffs) when browsing history. Now it&#8217;s impossible to see what patch does what.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
