<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Phil Dawes' Stuff - Latest Comments in Frequent code checkpointing with git</title><link>http://phildawesstuff.disqus.com/</link><description></description><atom:link href="https://phildawesstuff.disqus.com/frequent_code_checkpointing_with_git/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 22 Oct 2007 09:18:54 -0000</lastBuildDate><item><title>Re: Frequent code checkpointing with git</title><link>http://www.phildawes.net/blog/2007/10/20/frequent-code-checkpointing-with-git/#comment-2753627</link><description>&lt;p&gt;Have you tried using git-rebase -i ?  You need to give it the commit id of the last commit before your string of changes.  You can then tell it to combine all your commits into one (or more).&lt;/p&gt;&lt;p&gt;# *hack*&lt;br&gt;git commit -a -m"one"&lt;br&gt;# *hack*&lt;br&gt;git commit -a -m"two"&lt;br&gt;git rebase -i HEAD~2&lt;br&gt;# bring us an editor, select the "one" and "two" as squash, save, exit.&lt;br&gt;git log&lt;/p&gt;&lt;p&gt;An alternative workflow is to use git commit --amend.  But this does not keep your micro history around.  It just puts any recent changages into the last commit.&lt;/p&gt;&lt;p&gt;# *hack*&lt;br&gt;git commit -a -m"I am working on blah"&lt;br&gt;# *hack*&lt;br&gt;git commit --amend&lt;br&gt;...&lt;/p&gt;&lt;p&gt;-Bart&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bartman</dc:creator><pubDate>Mon, 22 Oct 2007 09:18:54 -0000</pubDate></item></channel></rss>