﻿<?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: Dealing with rejection in git, resetting your master to theirs and starting over</title>
	<atom:link href="http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/</link>
	<description>We're Just Programmers...</description>
	<lastBuildDate>Mon, 16 Jan 2012 07:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Justin</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-32</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sun, 04 Jul 2010 04:13:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-32</guid>
		<description>This is a different scenario than branching off the working set.
1) Assign myself a work item (contributing to an OSS project in my free time I get to pick)
2) Code/Compile/Test/Retest/Whatever
3) Commit working code
4) Push to my github branch
5) Send a pull request
6) Get a rejection (usually with a try again later)

So what I really need is a branch strategy that involves having a branch of mine thats always a pristine copy of their master, so I can rename my master with impunity.</description>
		<content:encoded><![CDATA[<p>This is a different scenario than branching off the working set.<br />
1) Assign myself a work item (contributing to an OSS project in my free time I get to pick)<br />
2) Code/Compile/Test/Retest/Whatever<br />
3) Commit working code<br />
4) Push to my github branch<br />
5) Send a pull request<br />
6) Get a rejection (usually with a try again later)</p>
<p>So what I really need is a branch strategy that involves having a branch of mine thats always a pristine copy of their master, so I can rename my master with impunity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-31</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 04 Jul 2010 04:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-31</guid>
		<description>Oh... and microsoft gave a name to what I described above. They call it &quot;shelving.&quot;

Whatever... its a branch off based on workspace.

They can call it magical for all I care. I&#039;ve been doing it for years.</description>
		<content:encoded><![CDATA[<p>Oh&#8230; and microsoft gave a name to what I described above. They call it &#8220;shelving.&#8221;</p>
<p>Whatever&#8230; its a branch off based on workspace.</p>
<p>They can call it magical for all I care. I&#8217;ve been doing it for years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-30</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 04 Jul 2010 04:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-30</guid>
		<description>It&#039;s a good habit to branch before the fact, but you can base your branch off your current working copy with svn.

I often find myself doing that at work when I take on a ticket that I think will be easy, then when 5:30 rolls around I just check my changes into a branch and resume the next day.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a good habit to branch before the fact, but you can base your branch off your current working copy with svn.</p>
<p>I often find myself doing that at work when I take on a ticket that I think will be easy, then when 5:30 rolls around I just check my changes into a branch and resume the next day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-28</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sun, 04 Jul 2010 03:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-28</guid>
		<description>I&#039;m not afraid of branches, just having trouble getting into the habit of branch per feature.

I&#039;ve been doing a branch after release at my current job with svn, and gotten one of my coworkers to consider it.

I do need to learn to branch before the fact, especially on my Saturday one man mongo hackathons. If I start the day with a 5-10 item todo list I should make 5-10 branches, cherry pick my commits back to my master and send a pull request.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not afraid of branches, just having trouble getting into the habit of branch per feature.</p>
<p>I&#8217;ve been doing a branch after release at my current job with svn, and gotten one of my coworkers to consider it.</p>
<p>I do need to learn to branch before the fact, especially on my Saturday one man mongo hackathons. If I start the day with a 5-10 item todo list I should make 5-10 branches, cherry pick my commits back to my master and send a pull request.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-27</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 04 Jul 2010 03:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-27</guid>
		<description>I&#039;m also not really sure why you are so afraid of branches.

If it takes you more than a day to write a piece of code... it should be in a branch.</description>
		<content:encoded><![CDATA[<p>I&#8217;m also not really sure why you are so afraid of branches.</p>
<p>If it takes you more than a day to write a piece of code&#8230; it should be in a branch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-26</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Sun, 04 Jul 2010 03:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-26</guid>
		<description>Subversion &gt; git</description>
		<content:encoded><![CDATA[<p>Subversion > git</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Dearing</title>
		<link>http://www.justaprogrammer.net/2010/07/03/dealing-with-rejection-in-git-resetting-your-master-to-theirs-and-starting-over/comment-page-1/#comment-55</link>
		<dc:creator>Justin Dearing</dc:creator>
		<pubDate>Sat, 03 Jul 2010 22:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.justaprogrammer.net/?p=171#comment-55</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;RT @TopsyRT: Dealing with rejection in git, resetting your master to theirs and starting over http://bit.ly/a8ZfsT&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">RT @TopsyRT: Dealing with rejection in git, resetting your master to theirs and starting over <a href="http://bit.ly/a8ZfsT" rel="nofollow">http://bit.ly/a8ZfsT</a></span></span></span></p>
]]></content:encoded>
	</item>
</channel>
</rss>

