<?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: My git svn workflow</title>
	<atom:link href="http://www.rapaul.com/2010/01/13/my-git-svn-workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rapaul.com/2010/01/13/my-git-svn-workflow/</link>
	<description>A technical blog written by Richard Paul</description>
	<lastBuildDate>Tue, 07 Feb 2012 02:12:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Paul</title>
		<link>http://www.rapaul.com/2010/01/13/my-git-svn-workflow/comment-page-1/#comment-1021</link>
		<dc:creator>Richard Paul</dc:creator>
		<pubDate>Sun, 13 Jun 2010 17:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rapaul.com/?p=417#comment-1021</guid>
		<description>@Gergely I&#039;m yet to have a need for merging multiple svn branches so I can&#039;t really comment on the situation.  But I no longer use Git&#039;s merge function.  Once I have committed code on my feature branch use Git&#039;s rebase feature to resolve any conflicts. e.g.
1) git checkout master
2) git svn rebase (to pick up changes)
3) git checkout mystorybranch (which has already been committed to)
4) git rebase master (this applies my changes on top of the upstream changes)
5) git mergetool (resolve conflicts if they exist, configured to use meld)
6) git add xyz (add the files you have merged)
7) git rebase --continue
8) git svn dcommit
9) git checkout master (read for the next story branch)

Steps 5,6,7 are only required if you have conflicts.</description>
		<content:encoded><![CDATA[<p>@Gergely I&#8217;m yet to have a need for merging multiple svn branches so I can&#8217;t really comment on the situation.  But I no longer use Git&#8217;s merge function.  Once I have committed code on my feature branch use Git&#8217;s rebase feature to resolve any conflicts. e.g.<br />
1) git checkout master<br />
2) git svn rebase (to pick up changes)<br />
3) git checkout mystorybranch (which has already been committed to)<br />
4) git rebase master (this applies my changes on top of the upstream changes)<br />
5) git mergetool (resolve conflicts if they exist, configured to use meld)<br />
6) git add xyz (add the files you have merged)<br />
7) git rebase &#8211;continue<br />
8) git svn dcommit<br />
9) git checkout master (read for the next story branch)</p>
<p>Steps 5,6,7 are only required if you have conflicts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gergely Nagy</title>
		<link>http://www.rapaul.com/2010/01/13/my-git-svn-workflow/comment-page-1/#comment-1018</link>
		<dc:creator>Gergely Nagy</dc:creator>
		<pubDate>Sat, 12 Jun 2010 20:46:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.rapaul.com/?p=417#comment-1018</guid>
		<description>@Richard, I&#039;m not Nic - but I guess local commits are also useful.

BTW, what do ye think about merging 2 svn branches using git? I read somewhere that dcommitting the merge result is not advisable, but not doing so would be pretty limiting - and not sure why is that.
Actually, the main reason I got tempted by git-svn is the help out with some complex svn merges.. and it does seem promising so far:)</description>
		<content:encoded><![CDATA[<p>@Richard, I&#8217;m not Nic &#8211; but I guess local commits are also useful.</p>
<p>BTW, what do ye think about merging 2 svn branches using git? I read somewhere that dcommitting the merge result is not advisable, but not doing so would be pretty limiting &#8211; and not sure why is that.<br />
Actually, the main reason I got tempted by git-svn is the help out with some complex svn merges.. and it does seem promising so far:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Paul</title>
		<link>http://www.rapaul.com/2010/01/13/my-git-svn-workflow/comment-page-1/#comment-584</link>
		<dc:creator>Richard Paul</dc:creator>
		<pubDate>Thu, 14 Jan 2010 10:59:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rapaul.com/?p=417#comment-584</guid>
		<description>@Nic Feature/story branches to allow for quick context switching and is the main reason I use Git. What are the benefits you see with Git besides cheap local branching?</description>
		<content:encoded><![CDATA[<p>@Nic Feature/story branches to allow for quick context switching and is the main reason I use Git. What are the benefits you see with Git besides cheap local branching?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nic Wise</title>
		<link>http://www.rapaul.com/2010/01/13/my-git-svn-workflow/comment-page-1/#comment-583</link>
		<dc:creator>Nic Wise</dc:creator>
		<pubDate>Thu, 14 Jan 2010 10:22:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rapaul.com/?p=417#comment-583</guid>
		<description>this is pretty much how I work, except I dont bother doing the feature branch - mostly because I dont need to. At the moment. Maybe I will shortly :)

I tend to use GitExtensions on windows. It&#039;s msysgit and a nice-ish UI on it. Makes staging files a lot easier for me, tho I end up using the command line  for almost eveything else.

My workflow is:

git init etc - only did this once, took ages.

work work work
git add etc
git commit as needed. repeat more work

git svn rebase
git svn dcommit

I think I dont need the rebase, &#039;cos it does that with the dcommit, but hey - habit.

I also have a patch which makes git svn work a LOT quicker (20secs vrs 2 mins) by dynamically loading the svn libs. Makes working with a very remote server (my svn is in denmark) a lot nicer.

:)</description>
		<content:encoded><![CDATA[<p>this is pretty much how I work, except I dont bother doing the feature branch &#8211; mostly because I dont need to. At the moment. Maybe I will shortly :)</p>
<p>I tend to use GitExtensions on windows. It&#8217;s msysgit and a nice-ish UI on it. Makes staging files a lot easier for me, tho I end up using the command line  for almost eveything else.</p>
<p>My workflow is:</p>
<p>git init etc &#8211; only did this once, took ages.</p>
<p>work work work<br />
git add etc<br />
git commit as needed. repeat more work</p>
<p>git svn rebase<br />
git svn dcommit</p>
<p>I think I dont need the rebase, &#8216;cos it does that with the dcommit, but hey &#8211; habit.</p>
<p>I also have a patch which makes git svn work a LOT quicker (20secs vrs 2 mins) by dynamically loading the svn libs. Makes working with a very remote server (my svn is in denmark) a lot nicer.</p>
<p>:)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

