<?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 Basics: Cleaning up excess branches</title>
	<atom:link href="http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/</link>
	<description>Your peek inside the collective mind of The Frontier Group</description>
	<lastBuildDate>Wed, 22 May 2013 04:35:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Git Basics: Cleaning up excess branches &#171; Coffee &#38; diamonds &#8211; Information about the Java and Ruby worlds!!!</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3931</link>
		<dc:creator>Git Basics: Cleaning up excess branches &#171; Coffee &#38; diamonds &#8211; Information about the Java and Ruby worlds!!!</dc:creator>
		<pubDate>Sun, 22 Jul 2012 14:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3931</guid>
		<description>[...] Read more&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Athayde</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3926</link>
		<dc:creator>John Athayde</dc:creator>
		<pubDate>Tue, 17 Jul 2012 17:24:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3926</guid>
		<description>You need to put them in a code block to get it to not auto parse the double dash into an em-dash</description>
		<content:encoded><![CDATA[<p>You need to put them in a code block to get it to not auto parse the double dash into an em-dash</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Rudolph</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3925</link>
		<dc:creator>Jason Rudolph</dc:creator>
		<pubDate>Tue, 17 Jul 2012 12:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3925</guid>
		<description>It looks like Wordpress decided to apply some unintended formatting to my comment above. There should be two dashes before &quot;prune&quot; and &quot;delete&quot;.

Let&#039;s see if this makes WordPress happy:

Fetch and prune: &lt;code&gt;git fetch --prune&lt;/code&gt;

Delete remote branch: &lt;code&gt;git push your_remote –delete branch_name&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>It looks like WordPress decided to apply some unintended formatting to my comment above. There should be two dashes before &#8220;prune&#8221; and &#8220;delete&#8221;.</p>
<p>Let&#8217;s see if this makes WordPress happy:</p>
<p>Fetch and prune: <code>git fetch --prune</code></p>
<p>Delete remote branch: <code>git push your_remote –delete branch_name</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valeriy</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3924</link>
		<dc:creator>Valeriy</dc:creator>
		<pubDate>Tue, 17 Jul 2012 09:10:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3924</guid>
		<description>&gt;&gt;&gt;You can easily write a bash script (or ruby, or whatever) that goes through (maybe as a cron job) and deletes merged branches.

You can use gitlab. There is function automerge branch with option &quot;delete source-branch&quot;</description>
		<content:encoded><![CDATA[<p>&gt;&gt;&gt;You can easily write a bash script (or ruby, or whatever) that goes through (maybe as a cron job) and deletes merged branches.</p>
<p>You can use gitlab. There is function automerge branch with option &#8220;delete source-branch&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Maguire</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3923</link>
		<dc:creator>Jordan Maguire</dc:creator>
		<pubDate>Tue, 17 Jul 2012 00:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3923</guid>
		<description>Nice - Thanks Jason and Uros.</description>
		<content:encoded><![CDATA[<p>Nice &#8211; Thanks Jason and Uros.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Rudolph</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3921</link>
		<dc:creator>Jason Rudolph</dc:creator>
		<pubDate>Mon, 16 Jul 2012 16:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3921</guid>
		<description>Good stuff!

As a bonus, recent versions of Git have added some usability improvements to make these tasks easier and more intuitive.

=== Fetch and Prune in One Step ===

Prior to Git 1.6.6, you needed two steps into order to fetch and prune:

    &lt;code&gt;git fetch
    git remote prune your_remote&lt;/code&gt;

As of Git 1.6.6, you can actually combine fetching and pruning in a single command.

    &lt;code&gt;git fetch --prune&lt;/code&gt;

=== Improved Syntax for Deleting Remote Branches  ===

I would argue that the original syntax is odd and a bit unintuitive for deleting remote branches:

    &lt;code&gt;git push your_remote :branch_name&lt;/code&gt;

Who thought &quot;:&quot; was a good indicator for &quot;delete&quot;? ;-)

As of Git 1.7.0, you can use this alternative syntax to delete remote branches:

    &lt;code&gt;git push your_remote --delete branch_name&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>Good stuff!</p>
<p>As a bonus, recent versions of Git have added some usability improvements to make these tasks easier and more intuitive.</p>
<p>=== Fetch and Prune in One Step ===</p>
<p>Prior to Git 1.6.6, you needed two steps into order to fetch and prune:</p>
<p>    <code>git fetch<br />
    git remote prune your_remote</code></p>
<p>As of Git 1.6.6, you can actually combine fetching and pruning in a single command.</p>
<p>    <code>git fetch --prune</code></p>
<p>=== Improved Syntax for Deleting Remote Branches  ===</p>
<p>I would argue that the original syntax is odd and a bit unintuitive for deleting remote branches:</p>
<p>    <code>git push your_remote :branch_name</code></p>
<p>Who thought &#8220;:&#8221; was a good indicator for &#8220;delete&#8221;? ;-)</p>
<p>As of Git 1.7.0, you can use this alternative syntax to delete remote branches:</p>
<p>    <code>git push your_remote --delete branch_name</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uros Jurglic</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3920</link>
		<dc:creator>Uros Jurglic</dc:creator>
		<pubDate>Mon, 16 Jul 2012 10:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3920</guid>
		<description>Good post!

One addition I use quite a lot - fetches remotes and prunes local that were deleted:
git fetch -p</description>
		<content:encoded><![CDATA[<p>Good post!</p>
<p>One addition I use quite a lot &#8211; fetches remotes and prunes local that were deleted:<br />
git fetch -p</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samuel Cochran</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3918</link>
		<dc:creator>Samuel Cochran</dc:creator>
		<pubDate>Sun, 15 Jul 2012 03:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3918</guid>
		<description>Like you mention, I use y shell to optimise this to only one interaction with remote (but not in cron):

&lt;code&gt;git push origin $(git branch -r --merged origin/master &#124; sed &quot;s/origin\\//:/&quot; &#124; egrep -v &quot;HEAD&#124;master&#124;develop&quot;)&lt;/code&gt;

If you want to see what it does first, chuck an &lt;code&gt;echo&lt;/code&gt; in front.</description>
		<content:encoded><![CDATA[<p>Like you mention, I use y shell to optimise this to only one interaction with remote (but not in cron):</p>
<p><code>git push origin $(git branch -r --merged origin/master | sed "s/origin\\//:/" | egrep -v "HEAD|master|develop")</code></p>
<p>If you want to see what it does first, chuck an <code>echo</code> in front.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mlambie</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3909</link>
		<dc:creator>mlambie</dc:creator>
		<pubDate>Tue, 10 Jul 2012 15:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3909</guid>
		<description>I love the gardening metaphors: pruning excess branches like you would a tree.</description>
		<content:encoded><![CDATA[<p>I love the gardening metaphors: pruning excess branches like you would a tree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Maguire</title>
		<link>http://blog.thefrontiergroup.com.au/2012/07/git-basics-cleaning-up-excess-branches/comment-page-1/#comment-3908</link>
		<dc:creator>Jordan Maguire</dc:creator>
		<pubDate>Tue, 10 Jul 2012 14:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.thefrontiergroup.com.au/?p=1991#comment-3908</guid>
		<description>Awesome Matt, glad I could help you out</description>
		<content:encoded><![CDATA[<p>Awesome Matt, glad I could help you out</p>
]]></content:encoded>
	</item>
</channel>
</rss>
