<?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: Git Beyond the D in DVCS</title>
	<atom:link href="http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/feed/" rel="self" type="application/rss+xml" />
	<link>http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/</link>
	<description>Git, .NET and more</description>
	<lastBuildDate>Mon, 01 Apr 2013 17:24:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Keith Dahlby</title>
		<link>http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/#comment-103</link>
		<dc:creator>Keith Dahlby</dc:creator>
		<pubDate>Sat, 15 Oct 2011 02:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/keithdahlby/?p=83#comment-103</guid>
		<description>There&#039;s really not much of a workflow to it. When you get to a point where you find yourself with overlapping logical changes in a file you can use &lt;code&gt;git add -p&lt;/code&gt; to stage and commit those changes in multiple parts.

The easiest way to see this in action is to make several changes then do a &lt;code&gt;git add -Ap&lt;/code&gt; to stage all files, piece by piece. For each hunk of changes you&#039;ll be presented with several options: the most important are y/n (do or do not include the current hunk) and s (split this hunk into smaller hunks). Once you&#039;ve staged something, try a &lt;code&gt;git reset -p&lt;/code&gt; to go in the other direction.</description>
		<content:encoded><![CDATA[<p>There&#8217;s really not much of a workflow to it. When you get to a point where you find yourself with overlapping logical changes in a file you can use <code>git add -p</code> to stage and commit those changes in multiple parts.</p>
<p>The easiest way to see this in action is to make several changes then do a <code>git add -Ap</code> to stage all files, piece by piece. For each hunk of changes you&#8217;ll be presented with several options: the most important are y/n (do or do not include the current hunk) and s (split this hunk into smaller hunks). Once you&#8217;ve staged something, try a <code>git reset -p</code> to go in the other direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domenic Denicola</title>
		<link>http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/#comment-102</link>
		<dc:creator>Domenic Denicola</dc:creator>
		<pubDate>Fri, 14 Oct 2011 13:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/keithdahlby/?p=83#comment-102</guid>
		<description>&gt; I use this feature on an almost daily basis to separate cosmetic changes
 from refactoring from new feature work, without having to undo some 
changes so that I can commit the others.

Can you expand on this? I&#039;ve often wanted some way to do this kind of thing, but cannot figure out from your brief description what the workflow would be.

Thanks for the great post!</description>
		<content:encoded><![CDATA[<p>&gt; I use this feature on an almost daily basis to separate cosmetic changes<br />
 from refactoring from new feature work, without having to undo some<br />
changes so that I can commit the others.</p>
<p>Can you expand on this? I&#8217;ve often wanted some way to do this kind of thing, but cannot figure out from your brief description what the workflow would be.</p>
<p>Thanks for the great post!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Meridth</title>
		<link>http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/#comment-101</link>
		<dc:creator>Jason Meridth</dc:creator>
		<pubDate>Fri, 14 Oct 2011 13:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/keithdahlby/?p=83#comment-101</guid>
		<description>Excellent post.  There are a few tricks in there I have never used.  Thank you for sharing them Keith.</description>
		<content:encoded><![CDATA[<p>Excellent post.  There are a few tricks in there I have never used.  Thank you for sharing them Keith.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Morning Brew - Chris Alcock &#187; The Morning Brew #959</title>
		<link>http://lostechies.com/keithdahlby/2011/10/14/git-beyond-the-d-in-dvcs/#comment-100</link>
		<dc:creator>The Morning Brew - Chris Alcock &#187; The Morning Brew #959</dc:creator>
		<pubDate>Fri, 14 Oct 2011 07:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://lostechies.com/keithdahlby/?p=83#comment-100</guid>
		<description>[...] Git Beyond the D in DVCS - Keith Dahlby joins in the discussion highlighting some of the key features of the Git DVCS and how he uses them. [...]</description>
		<content:encoded><![CDATA[<p>[...] Git Beyond the D in DVCS &#8211; Keith Dahlby joins in the discussion highlighting some of the key features of the Git DVCS and how he uses them. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
