<?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: Partial &#8216;svn dcommit&#8217; with git</title>
	<atom:link href="http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/feed/" rel="self" type="application/rss+xml" />
	<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/</link>
	<description>Open Source, The Web, And German-American Oddities</description>
	<lastBuildDate>Sat, 31 Mar 2012 00:13:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: codequan.com &#187; Partial ’svn dcommit’ with git</title>
		<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/comment-page-1/#comment-247367</link>
		<dc:creator>codequan.com &#187; Partial ’svn dcommit’ with git</dc:creator>
		<pubDate>Tue, 26 Jan 2010 08:12:50 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/?p=2516#comment-247367</guid>
		<description>[...] found this nice article about how to send only a partial set of changes. Essentially the idea is to use &#8216;git rebase [...]</description>
		<content:encoded><![CDATA[<p>[...] found this nice article about how to send only a partial set of changes. Essentially the idea is to use &#8216;git rebase [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/comment-page-1/#comment-245176</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Sat, 02 Jan 2010 18:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/?p=2516#comment-245176</guid>
		<description>Thanks for your thoughts, guys. Making a temporary branch for this purpose sounds like a great idea as well -- in spite of it being a little more work, at least you can&#039;t hose your work by accidentally screwing up the rebase.

Mook: &lt;em&gt;as one line in the shell to reduce the chances of me clobbering somebody else’s commit&lt;/em&gt; -- if I understand you right, you don&#039;t need to worry about this. Commits to SVN (and hopefully any other VCS) are atomic. If the repo has changed since you last touched it, your commit will fail, but you will never ever plaster over someone else&#039;s commit.</description>
		<content:encoded><![CDATA[<p>Thanks for your thoughts, guys. Making a temporary branch for this purpose sounds like a great idea as well &#8212; in spite of it being a little more work, at least you can&#8217;t hose your work by accidentally screwing up the rebase.</p>
<p>Mook: <em>as one line in the shell to reduce the chances of me clobbering somebody else’s commit</em> &#8212; if I understand you right, you don&#8217;t need to worry about this. Commits to SVN (and hopefully any other VCS) are atomic. If the repo has changed since you last touched it, your commit will fail, but you will never ever plaster over someone else&#8217;s commit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mook</title>
		<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/comment-page-1/#comment-245042</link>
		<dc:creator>Mook</dc:creator>
		<pubDate>Fri, 01 Jan 2010 06:27:51 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/?p=2516#comment-245042</guid>
		<description>I&#039;ve always found it more calming to my nerves to use a temporary branch for things like this - give your current master a new branch name (typically &quot;wip&quot;), reset/rebase-i master to the state I want to commit, and git svn rebase &amp;&amp; git svn dcommit (as one line in the shell to reduce the chances of me clobbering somebody else&#039;s commit).  Of course, I also normally pair it with dcommit -vn, so maybe I&#039;m just paranoid :)</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always found it more calming to my nerves to use a temporary branch for things like this &#8211; give your current master a new branch name (typically &#8220;wip&#8221;), reset/rebase-i master to the state I want to commit, and git svn rebase &amp;&amp; git svn dcommit (as one line in the shell to reduce the chances of me clobbering somebody else&#8217;s commit).  Of course, I also normally pair it with dcommit -vn, so maybe I&#8217;m just paranoid <img src='http://fredericiana.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Orem</title>
		<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/comment-page-1/#comment-245008</link>
		<dc:creator>Jeremy Orem</dc:creator>
		<pubDate>Thu, 31 Dec 2009 23:17:20 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/?p=2516#comment-245008</guid>
		<description>Nice! Also, if you just want to delete all the unwanted commits instead of marking them &quot;edit&quot; you can do:

git checkout -b svn_commit
git rebase -i HEAD~4 (or whatever)
(reorder the commits and delete the ones you don&#039;t want)
git svn dcommit
git checkout master
git svn rebase
git branch -d svn_commit</description>
		<content:encoded><![CDATA[<p>Nice! Also, if you just want to delete all the unwanted commits instead of marking them &#8220;edit&#8221; you can do:</p>
<p>git checkout -b svn_commit<br />
git rebase -i HEAD~4 (or whatever)<br />
(reorder the commits and delete the ones you don&#8217;t want)<br />
git svn dcommit<br />
git checkout master<br />
git svn rebase<br />
git branch -d svn_commit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Balogh</title>
		<link>http://fredericiana.com/2009/12/31/partial-svn-dcommit-with-git/comment-page-1/#comment-244967</link>
		<dc:creator>Jeff Balogh</dc:creator>
		<pubDate>Thu, 31 Dec 2009 15:38:36 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/?p=2516#comment-244967</guid>
		<description>Back in my remora days, I got this done by checking out HEAD~N in step 2 and then going back to master in step 4.  I don&#039;t think anything went wrong, but I was always worried about rebasing and what would happen to those future commits.  dcommitting during a `rebase -i` seems like a much better idea.</description>
		<content:encoded><![CDATA[<p>Back in my remora days, I got this done by checking out HEAD~N in step 2 and then going back to master in step 4.  I don&#8217;t think anything went wrong, but I was always worried about rebasing and what would happen to those future commits.  dcommitting during a `rebase -i` seems like a much better idea.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

