<?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: History as documentation</title>
	<atom:link href="http://blog.ezyang.com/2010/02/history-as-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ezyang.com/2010/02/history-as-documentation/</link>
	<description>Existential Pontification and Generalized Abstract Digressions</description>
	<lastBuildDate>Sun, 05 Feb 2012 23:02:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Edward Z. Yang</title>
		<link>http://blog.ezyang.com/2010/02/history-as-documentation/comment-page-1/#comment-652</link>
		<dc:creator>Edward Z. Yang</dc:creator>
		<pubDate>Thu, 08 Jul 2010 00:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ezyang.com/?p=439#comment-652</guid>
		<description>The standard format is a one-line short description, and then a longer description following it. The Git tools will take advantage of this, since there are abbreviated log formats that just take the first line.

Beyond that, the format is very dependent on your circumstance. When I am developing something actively to begin with, I will frequently omit the longer commit message, since the changes come quickly and don’t need much thought. If I commit in a codebase with multiple other active developers, I tailor my message to make it clear to them what my change is about with minimal effort.</description>
		<content:encoded><![CDATA[<p>The standard format is a one-line short description, and then a longer description following it. The Git tools will take advantage of this, since there are abbreviated log formats that just take the first line.</p>
<p>Beyond that, the format is very dependent on your circumstance. When I am developing something actively to begin with, I will frequently omit the longer commit message, since the changes come quickly and don’t need much thought. If I commit in a codebase with multiple other active developers, I tailor my message to make it clear to them what my change is about with minimal effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.ezyang.com/2010/02/history-as-documentation/comment-page-1/#comment-634</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 04 Jul 2010 09:35:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ezyang.com/?p=439#comment-634</guid>
		<description>Nice tip about descriptive commit messages. Do you have any recommendations for a good format for larger commit messages?</description>
		<content:encoded><![CDATA[<p>Nice tip about descriptive commit messages. Do you have any recommendations for a good format for larger commit messages?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils Jonsson</title>
		<link>http://blog.ezyang.com/2010/02/history-as-documentation/comment-page-1/#comment-632</link>
		<dc:creator>Nils Jonsson</dc:creator>
		<pubDate>Sun, 04 Jul 2010 01:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ezyang.com/?p=439#comment-632</guid>
		<description>@Anonymous http://book.git-scm.com/4_interactive_rebasing.html</description>
		<content:encoded><![CDATA[<p>@Anonymous <a href="http://book.git-scm.com/4_interactive_rebasing.html" rel="nofollow">http://book.git-scm.com/4_interactive_rebasing.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.ezyang.com/2010/02/history-as-documentation/comment-page-1/#comment-631</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 03 Jul 2010 11:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ezyang.com/?p=439#comment-631</guid>
		<description>What exactly is the &quot;history rewriting&quot; thing you&#039;re mentioning in the last paragraph? Is it a Git feature?

Anyway, great post as always. Really inspiring.</description>
		<content:encoded><![CDATA[<p>What exactly is the &#8220;history rewriting&#8221; thing you&#8217;re mentioning in the last paragraph? Is it a Git feature?</p>
<p>Anyway, great post as always. Really inspiring.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

