<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Blue Cog Blog &#187; Git</title>
	<atom:link href="http://www.bluecog.com/blog/tag/git/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bluecog.com/blog</link>
	<description>It's just a freaking blue cog...</description>
	<lastBuildDate>Thu, 22 Dec 2011 01:21:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Installing Git From Source On Ubuntu</title>
		<link>http://www.bluecog.com/blog/2010/08/03/installing-git-from-source-on-ubuntu/</link>
		<comments>http://www.bluecog.com/blog/2010/08/03/installing-git-from-source-on-ubuntu/#comments</comments>
		<pubDate>Tue, 03 Aug 2010 19:32:59 +0000</pubDate>
		<dc:creator>Bill Melvin</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Git]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.bluecog.com/blog/?p=676</guid>
		<description><![CDATA[ [...]]]></description>
			<content:encoded><![CDATA[<p>Git is available from the Ubuntu repositories in the git-core, git-doc, and git-gui packages (there are other Git-related packages available but I think those three make up a basic installation). The package maintainer&#8217;s version tends to be behind the currently available version of Git. To have the latest features and fixes in Git it is necessary to install it from source. This is the process I use to install Git from source on Ubuntu 9.10 (karmic) and 10.04 (lucid):</p>
<p>Download the source archive from <a href="http://git-scm.com">http://git-scm.com</a> and extract it (I just extract it where it lands in my Downloads directory). Open a terminal in (or <code>cd</code> to) the extracted Git source directory (<code>~/Downloads/git-1.7.2.1</code> as of my latest install). </p>
<p>Install required packages:</p>
<pre class="brush: bash">
sudo apt-get install libcurl4-gnutls-dev libexpat1-dev libssl-dev gettext libz-dev asciidoc
</pre>
<p>Build and install Git and its documentation:</p>
<pre class="brush: bash">
make prefix=/usr/local all doc
sudo make prefix=/usr/local install install-doc
</pre>
<p>If you don&#8217;t include the <code>doc</code> and <code>install-doc</code> tasks in the installation then the Git documentation will not be available via man pages or the <code>git help</code> command. If you don&#8217;t want the documentation then you can leave out those tasks and you won&#8217;t need to install the <code>asciidoc</code> package either. I prefer to have the documentation.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bluecog.com/blog/2010/08/03/installing-git-from-source-on-ubuntu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tweaking the Bash Prompt</title>
		<link>http://www.bluecog.com/blog/2010/07/03/tweaking-the-bash-prompt/</link>
		<comments>http://www.bluecog.com/blog/2010/07/03/tweaking-the-bash-prompt/#comments</comments>
		<pubDate>Sat, 03 Jul 2010 13:24:30 +0000</pubDate>
		<dc:creator>Bill Melvin</dc:creator>
				<category><![CDATA[Computer User]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[Git]]></category>
		<category><![CDATA[Ubuntu]]></category>

		<guid isPermaLink="false">http://www.bluecog.com/blog/?p=636</guid>
		<description><![CDATA[ [...]]]></description>
			<content:encoded><![CDATA[<p>A little Saturday morning tweaking.</p>
<p>Based on <a href="http://railstips.org/blog/archives/2009/02/02/bedazzle-your-bash-prompt-with-git-info/">this</a> post at railstips.org, I decided to adjust my Bash prompt by appending the following to my <strong>~/.bashrc</strong> file:</p>
<pre class="brush: bash">
#...

function parse_git_branch {
  ref=$(git symbolic-ref HEAD 2&gt; /dev/null) || return
  echo &quot;(&quot;${ref#refs/heads/}&quot;)&quot;
}

BLACK=&quot;\[\033[0;30m\]&quot;
BLUE=&quot;\[\033[0;34m\]&quot;
VIOLET=&quot;\[\033[1;35m\]&quot;
CYAN=&quot;\[\033[0;36m\]&quot;

PS1=&quot;\n[$CYAN\u@\h:$BLUE\w$VIOLET \$(parse_git_branch)$BLACK]\n\$ &quot;
</pre>
<p>The prompt will now show the name of the branch I am working in when the current directory is part of a Git repository. The original code used yellow, red, and green to highlight parts of the prompt. That messed with my mind when I ran RSpec and saw yellow and red when I was expecting all green. Rather than get used to it, I changed the colors. I also added some newlines to perhaps keep the command line neater when deep in a directory tree.</p>
<p style="text-align: center;"><a href="http://www.bluecog.com/blog/wp-content/uploads/2010/07/terminal_20100703_0909.png"><img class="size-medium wp-image-642 aligncenter" style="border: 1px solid black;" title="Terminal" src="http://www.bluecog.com/blog/wp-content/uploads/2010/07/terminal_20100703_0909-300x139.png" alt="Terminal screen shot" width="300" height="139" /></a></p>
<p>&nbsp;</p>
<p><em>[Update 2010-07-23]</em></p>
<p>After running with the above settings for a while I decided I don&#8217;t care for the colors in the prompt. Don&#8217;t need the square brackets either. I do like seeing the current git branch. That simplifies things a bit.</p>
<pre class="brush: bash">
#...

function parse_git_branch {
  ref=$(git symbolic-ref HEAD 2&gt; /dev/null) || return
  echo &quot;(&quot;${ref#refs/heads/}&quot;)&quot;
}

PS1=&quot;\n\u@\h:\w  \$(parse_git_branch)\n\$ &quot;
</pre>
<p>&nbsp;</p>
<p><em>[Update 2010-09-25]</em></p>
<p>Okay, maybe a little color&#8230;</p>
<pre class="brush: bash">
#...

function parse_git_branch {
  ref=$(git symbolic-ref HEAD 2&gt; /dev/null) || return
  echo &quot;(&quot;${ref#refs/heads/}&quot;)&quot;
}

VIOLET=&quot;\[\033[1;35m\]&quot;
NO_COLOR=&quot;\[\033[0;0m\]&quot;  

PS1=&quot;\n$VIOLET\u@\h:\w  \$(parse_git_branch)$NO_COLOR\n\$ &quot;
</pre>
<p>See. I told you it was &quot;tweaking.&quot;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bluecog.com/blog/2010/07/03/tweaking-the-bash-prompt/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Git Resources</title>
		<link>http://www.bluecog.com/blog/2010/03/02/git-resources/</link>
		<comments>http://www.bluecog.com/blog/2010/03/02/git-resources/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 17:27:16 +0000</pubDate>
		<dc:creator>Bill Melvin</dc:creator>
				<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Git]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[SCM]]></category>

		<guid isPermaLink="false">http://www.bluecog.com/blog/?p=549</guid>
		<description><![CDATA[ [...]]]></description>
			<content:encoded><![CDATA[<p>I have been learning to use Git. The following is a list of resources I found to be useful, interesting, or that I want to explore further as I get into Git:<br />
<a href="http://www.bluecog.com/blog/wp-content/uploads/2010/03/GitYummyTrees.png"><img src="http://www.bluecog.com/blog/wp-content/uploads/2010/03/GitYummyTrees.png" alt="" title="GitYummyTrees" width="101" height="98" class="alignright size-full wp-image-566" /></a><br />
Website: <a href="http://git-scm.com/">Git &#8211; Fast Version Control System</a> &#8211; The home of Git. When you think <em>source code management</em> it&#8217;s only natural to picture a monster eating trees.</p>
<p>Book: <a href="http://progit.org/">Book &#8211; Pro Git &#8211; by Scott Chacon</a> &#8211; Concise coverage of using Git. You can purchase the book or read the whole book online.</p>
<p>Book: <a href="http://my.safaribooksonline.com/9780596158187">Safari Books Online: Version Control with Git, 1st Edition</a></p>
<p>Tool: <a href="http://code.google.com/p/msysgit/">msysgit</a> &#8211; Run Git on Windows from a specialized BASH prompt.</p>
<p><em>[Update 2010-07-03: Changed the order of the list so the resources I have used the most are above this note.]</em></p>
<p>Website: <a href="http://github.com/">GitHub &#8211; Secure Git hosting and collaborative development</a></p>
<p>Video: <a href="http://www.oreillynet.com/pub/e/1394?utm_source=feedburner&#038;utm_medium=feed&#038;utm_campaign=Feed%3A+oreilly%2Fnews+%28O%27Reilly+News%29&#038;utm_content=Google+Reader">Webcast: Git in One Hour</a> &#8211; Scott Chacon shows a lot of what he covers in his book in this screencast.</p>
<p>Video: <a href="http://vimeo.com/9324683">James Gregory on Git</a> &#8211; <a href="http://jagregory.com/">James Gregory</a> does a screencast on Git as well.</p>
<p>Website: <a href="http://gitready.com/">git ready &#8211; learn git one commit at a time</a> </p>
<p>Article: <a href="http://utsl.gen.nz/talks/git-svn/intro.html">An introduction to git-svn for Subversion/SVK users and deserters</a></p>
<p>Article: <a href="http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way">scie.nti.st &#8211; Hosting Git repositories, The Easy (and Secure) Way</a> &#8211; Gitosis.</p>
<p>Article: <a href="http://blog.wekeroad.com/2009/11/23/deploying-a-web-application-with-git-and-ftp?utm_source=feedburner&#038;utm_medium=feed&#038;utm_campaign=Feed%3A+wekeroad%2FEeKc+%28Rob+Conery%29&#038;utm_content=Google+Reader">Deploying A Web Application with Git and FTP</a> &#8211; Rob Conery shows one way he uses Git.</p>
<p>Article: <a href="http://www.lostechies.com/blogs/jason_meridth/archive/2009/06/01/git-for-windows-developers-git-series-part-1.aspx">Git For Windows Developers – Git Series &#8211; Part 1 &#8211; Jason Meridth &#8211; Los Techies</a> &#8211; Describes using msysgit.</p>
<p>Article: <a href="http://www.lostechies.com/blogs/derickbailey/archive/2010/02/03/branch-per-feature-how-i-manage-subversion-with-git-branches.aspx">Branch-Per-Feature &#8211;  How I Manage Subversion With Git Branches &#8211; Los Techies</a></p>
<p>Article: <a href="http://www.lostechies.com/blogs/jagregory/archive/2009/11/25/git-s-guts-branches-head-and-fast-forwards.aspx">Git&#39;s guts: Branches, HEAD, and fast-forwards &#8211; James Gregory&#39;s Blog &#8211; Los Techies</a></p>
<p>Article: <a href="http://martinfowler.com/bliki/VersionControlTools.html">Martin Fowler &#8211; Version Control Tools</a> &#8211; Not about Git specifically. </p>
<p>Article: <a href="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html">ReinH &#8211; A Git Workflow for Agile Teams</a></p>
<p>Article: <a href="http://blog.weiskotten.com/2009/04/my-git-workflow.html">Jer on Rails &#8211; My Git Workflow</a></p>
<p>Article: <a href="http://justinfrench.com/index.php?id=253">JustinFrench.com &#8211; Git Aliases Rock</a></p>
<p>Article: <a href="http://github.com/guides/put-your-git-branch-name-in-your-shell-prompt">GitHub &#8211; Guides &#8211; Put your git branch name in your shell prompt</a></p>
<p>Article: <a href="http://www.tpope.net/node/106">A Note About Git Commit Messages | tpope.net</a></p>
<p>Article/Tool: <a href="http://michael-bien.com/mbien/entry/netbeans_git_plugin">Michael Bien&#39;s Weblog &#8211; NetBeans GIT support</a> &#8211; I have not tried the NBGit plugin yet but I have been playing with NetBeans a bit.</p>
<p>Podcast: <a href="http://www.hanselman.com/blog/HanselminutesPodcast108ExploringDistributedSourceControlWithGit.aspx">Hanselminutes Podcast 108 &#8211; Exploring Distributed Source Control with Git</a></p>
<p>Tool: <a href="http://github.com/webmat/git_remote_branch">git_remote_branch</a></p>
<p>Tool: <a href="http://code.google.com/p/tortoisegit/">tortoisegit</a> &#8211; Maybe like TortoiseSVN. I have not tried it.</p>
<p>Tool: <a href="http://www.eclipse.org/egit/">EGit</a> &#8211; Git plugin for Eclipse. I have not tried it.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bluecog.com/blog/2010/03/02/git-resources/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

