<?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>Brent Sordyl's blog &#187; git</title>
	<atom:link href="http://www.sordyl.info/tag/git/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sordyl.info</link>
	<description>Daily links to e-Learning and Web Technology resources</description>
	<lastBuildDate>Thu, 09 Sep 2010 17:00:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>gerrit &#8211; Project Hosting on Google Code</title>
		<link>http://www.sordyl.info/2010/07/25/links2/</link>
		<comments>http://www.sordyl.info/2010/07/25/links2/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 20:00:01 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the [...]]]></description>
			<content:encoded><![CDATA[<p>
Gerrit is a web based code review system, facilitating online code reviews for projects using the Git version control system.</p>
<p>Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.</p>
<p>Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer. This functionality enables a more centralized usage of Gi<br />
(Link: <a class="deliciouslink" href="http://code.google.com/p/gerrit/" title="gerrit - Project Hosting on Google Code" target="_blank">gerrit &#8211; Project Hosting on Google Code</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/07/25/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>William&#8217;s miscellaneous git tools</title>
		<link>http://www.sordyl.info/2010/07/23/links1/</link>
		<comments>http://www.sordyl.info/2010/07/23/links1/#comments</comments>
		<pubDate>Fri, 23 Jul 2010 15:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Here are a bunch of git-related tools I&#8217;ve found useful at some point. The git repository for all of these is cloneable at git://gitorious.org/willgit/mainline.git/ (browse).
git-wtf: understand the current state of your git repository.
git-publish-branch: publish a branch to a remote repository.
git-rank-contributors: rank all authors by patch size.
git-show-merges: show which branches are merged into the current branch.
git-walkthrough-add: [...]]]></description>
			<content:encoded><![CDATA[<p>
Here are a bunch of git-related tools I&#8217;ve found useful at some point. The git repository for all of these is cloneable at git://gitorious.org/willgit/mainline.git/ (browse).</p>
<p>git-wtf: understand the current state of your git repository.<br />
git-publish-branch: publish a branch to a remote repository.<br />
git-rank-contributors: rank all authors by patch size.<br />
git-show-merges: show which branches are merged into the current branch.<br />
git-walkthrough-add: (deprecated) like git add -p.<br />
(Link: <a class="deliciouslink" href="http://git-wt-commit.rubyforge.org/" title="William's miscellaneous git tools" target="_blank">William&#8217;s miscellaneous git tools</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/07/23/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>git ready » learn git one commit at a time</title>
		<link>http://www.sordyl.info/2010/07/22/links1/</link>
		<comments>http://www.sordyl.info/2010/07/22/links1/#comments</comments>
		<pubDate>Thu, 22 Jul 2010 21:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
earn git one commit at a time
(Link: git ready » learn git one commit at a time)
]]></description>
			<content:encoded><![CDATA[<p>
earn git one commit at a time<br />
(Link: <a class="deliciouslink" href="http://www.gitready.com/" title="git ready » learn git one commit at a time" target="_blank">git ready » learn git one commit at a time</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/07/22/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Git for the lazy &#8211; Spheriki</title>
		<link>http://www.sordyl.info/2010/06/18/links3/</link>
		<comments>http://www.sordyl.info/2010/06/18/links3/#comments</comments>
		<pubDate>Fri, 18 Jun 2010 18:00:03 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[scm]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Git is a distributed version control system. No, you don&#8217;t need to know what that means to use this guide. Think of it as a time machine: Subversion or CVS without the cruft.
If you make a lot of changes, but decided you made a mistake, this will save your butt.
This guide is for people who [...]]]></description>
			<content:encoded><![CDATA[<p>
Git is a distributed version control system. No, you don&#8217;t need to know what that means to use this guide. Think of it as a time machine: Subversion or CVS without the cruft.<br />
If you make a lot of changes, but decided you made a mistake, this will save your butt.<br />
This guide is for people who want to jump to any point in time with their project/game/whatever, and want something to use for themselves.<br />
(Link: <a class="deliciouslink" href="http://www.spheredev.org/wiki/Git_for_the_lazy" title="Git for the lazy - Spheriki" target="_blank">Git for the lazy &#8211; Spheriki</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/06/18/links3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Git Reference</title>
		<link>http://www.sordyl.info/2010/06/11/links1/</link>
		<comments>http://www.sordyl.info/2010/06/11/links1/#comments</comments>
		<pubDate>Fri, 11 Jun 2010 15:00:01 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
This is the Git reference site. This is meant to be a quick reference for learning and remembering the most important and commonly used Git commands. The commands are organized into sections of the type of operation you may be trying to do, and will preset the common options and commands needed to accomplish these [...]]]></description>
			<content:encoded><![CDATA[<p>
This is the Git reference site. This is meant to be a quick reference for learning and remembering the most important and commonly used Git commands. The commands are organized into sections of the type of operation you may be trying to do, and will preset the common options and commands needed to accomplish these common tasks.</p>
<p>Each section will link to the next section, so it can be used as a tutorial. Every page will also link to more in-depth Git documentation such as the offical manual pages and relevant sections in the Pro Git book, so you can learn more about any of the commands. First, we&#8217;ll start with thinking about source code management like Git does.<br />
(Link: <a class="deliciouslink" href="http://gitref.org/" title="Git Reference" target="_blank">Git Reference</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/06/11/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Gitbox — Git GUI for Mac OS X</title>
		<link>http://www.sordyl.info/2010/06/11/links2/</link>
		<comments>http://www.sordyl.info/2010/06/11/links2/#comments</comments>
		<pubDate>Fri, 11 Jun 2010 15:00:01 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[osx]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Gitbox is a Mac OS X graphical interface for Git version control system. In a single window you see branches, history and working directory status.
Everyday operations are easy: stage and unstage changes with a checkbox. Commit, pull, merge and push with a single click. Double-click a change to show a diff with FileMerge.app.
(Link: Gitbox — [...]]]></description>
			<content:encoded><![CDATA[<p>
Gitbox is a Mac OS X graphical interface for Git version control system. In a single window you see branches, history and working directory status.</p>
<p>Everyday operations are easy: stage and unstage changes with a checkbox. Commit, pull, merge and push with a single click. Double-click a change to show a diff with FileMerge.app.<br />
(Link: <a class="deliciouslink" href="http://gitbox.pierlis.com/" title="Gitbox — Git GUI for Mac OS X" target="_blank">Gitbox — Git GUI for Mac OS X</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/06/11/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>git-wtf</title>
		<link>http://www.sordyl.info/2010/05/08/links2/</link>
		<comments>http://www.sordyl.info/2010/05/08/links2/#comments</comments>
		<pubDate>Sat, 08 May 2010 20:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
A useful script that displays local &#038; remote branches, what are in sync and what need merging,
and so on, like so:
(Link: git-wtf)
]]></description>
			<content:encoded><![CDATA[<p>
A useful script that displays local &#038; remote branches, what are in sync and what need merging,<br />
and so on, like so:<br />
(Link: <a class="deliciouslink" href="http://github.com/michaelklishin/git-wtf" title="git-wtf" target="_blank">git-wtf</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/05/08/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ruby on Rails Tutorial: Version control with Git</title>
		<link>http://www.sordyl.info/2010/02/22/links1/</link>
		<comments>http://www.sordyl.info/2010/02/22/links1/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 16:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[rubyonrails]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Putting your source code under version control with Git is strongly recommended, not only because it’s nearly a universal practice in the Rails world, but also because it will allow you to share your code more easily (Section 1.3.4) and deploy your application right here in the first chapter (Section 1.4).
(Link: Ruby on Rails Tutorial: [...]]]></description>
			<content:encoded><![CDATA[<p>
Putting your source code under version control with Git is strongly recommended, not only because it’s nearly a universal practice in the Rails world, but also because it will allow you to share your code more easily (Section 1.3.4) and deploy your application right here in the first chapter (Section 1.4).<br />
(Link: <a class="deliciouslink" href="http://www.railstutorial.org/chapters/beginning#sec:version_control" title="Ruby on Rails Tutorial: Version control with Git" target="_blank">Ruby on Rails Tutorial: Version control with Git</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/02/22/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Visual Git Reference</title>
		<link>http://www.sordyl.info/2010/02/18/links3/</link>
		<comments>http://www.sordyl.info/2010/02/18/links3/#comments</comments>
		<pubDate>Thu, 18 Feb 2010 17:00:02 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[(Link: A Visual Git Reference)
]]></description>
			<content:encoded><![CDATA[<p>(Link: <a class="deliciouslink" href="http://marklodato.github.com/visual-git-guide/index-svg.html" title="A Visual Git Reference" target="_blank">A Visual Git Reference</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/02/18/links3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>repo.or.cz &#8211; Public Git Hosting</title>
		<link>http://www.sordyl.info/2010/02/08/links5/</link>
		<comments>http://www.sordyl.info/2010/02/08/links5/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 15:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[opensource]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
repo.or.cz is a public Git hosting site. Create a project in a snap, publish your development, give others push access and let anyone have a look and contribute. Alternatively, if you just see a random git:// URL fly by and want to check it out, or you have limited bandwidth or want backup &#8211; just [...]]]></description>
			<content:encoded><![CDATA[<p>
repo.or.cz is a public Git hosting site. Create a project in a snap, publish your development, give others push access and let anyone have a look and contribute. Alternatively, if you just see a random git:// URL fly by and want to check it out, or you have limited bandwidth or want backup &#8211; just quickly set up a mirror of any project published elsewhere and we will provide pull and gitweb access for the project, or send you notifications when new stuff gets committed. (read more, terms of use) (want to help?)<br />
(Link: <a class="deliciouslink" href="http://repo.or.cz/" title="repo.or.cz - Public Git Hosting" target="_blank">repo.or.cz &#8211; Public Git Hosting</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/02/08/links5/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Repository Hosting &#8211; Subversion Hosting, Git Hosting and Trac Hosting</title>
		<link>http://www.sordyl.info/2010/02/08/links7/</link>
		<comments>http://www.sordyl.info/2010/02/08/links7/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 15:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[scm]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Unlimited Repositories
Unlimited Trac Projects
Unlimited Users
Custom Domains
Custom Logos &#038; Colors
SSL Secured
WebDAV Shared Drives
Scheduled Backups
2GB Storage
$1/GB Additional Storage
(Link: Repository Hosting &#8211; Subversion Hosting, Git Hosting and Trac Hosting)
]]></description>
			<content:encoded><![CDATA[<p>
Unlimited Repositories<br />
Unlimited Trac Projects<br />
Unlimited Users<br />
Custom Domains<br />
Custom Logos &#038; Colors<br />
SSL Secured<br />
WebDAV Shared Drives<br />
Scheduled Backups<br />
2GB Storage<br />
$1/GB Additional Storage<br />
(Link: <a class="deliciouslink" href="http://repositoryhosting.com/" title="Repository Hosting - Subversion Hosting, Git Hosting and Trac Hosting" target="_blank">Repository Hosting &#8211; Subversion Hosting, Git Hosting and Trac Hosting</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/02/08/links7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>toto is a git-powered, minimalist blog engine for the hackers of Oz</title>
		<link>http://www.sordyl.info/2010/02/04/links1/</link>
		<comments>http://www.sordyl.info/2010/02/04/links1/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 15:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[blog]]></category>
		<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
toto is a git-powered, minimalist blog engine for the hackers of Oz. The engine weighs around ~230 sloc at its worst. There is no toto client, at least for now; everything goes through git.
(Link: toto is a git-powered, minimalist blog engine for the hackers of Oz)
]]></description>
			<content:encoded><![CDATA[<p>
toto is a git-powered, minimalist blog engine for the hackers of Oz. The engine weighs around ~230 sloc at its worst. There is no toto client, at least for now; everything goes through git.<br />
(Link: <a class="deliciouslink" href="http://cloudhead.io/toto" title="toto is a git-powered, minimalist blog engine for the hackers of Oz" target="_blank">toto is a git-powered, minimalist blog engine for the hackers of Oz</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/02/04/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting the Hang of GitHub &#124; Nettuts+</title>
		<link>http://www.sordyl.info/2010/01/12/links1/</link>
		<comments>http://www.sordyl.info/2010/01/12/links1/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 15:00:03 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[github]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
A project is always more fun when you&#8217;ve got friends working with you, but how can do it when working on a coding project? I&#8217;ll keep my keyboard to myself, thanks.
Enter GitHub. With this web service, you can share your coding projects and collaborate with ease!
(Link: Getting the Hang of GitHub &#124; Nettuts+)
]]></description>
			<content:encoded><![CDATA[<p>
A project is always more fun when you&#8217;ve got friends working with you, but how can do it when working on a coding project? I&#8217;ll keep my keyboard to myself, thanks.</p>
<p>Enter GitHub. With this web service, you can share your coding projects and collaborate with ease!<br />
(Link: <a class="deliciouslink" href="http://net.tutsplus.com/tutorials/other/getting-the-hang-of-github/" title="Getting the Hang of GitHub | Nettuts+" target="_blank">Getting the Hang of GitHub | Nettuts+</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/01/12/links1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>ReinH — A Git Workflow for Agile Teams</title>
		<link>http://www.sordyl.info/2010/01/04/links9/</link>
		<comments>http://www.sordyl.info/2010/01/04/links9/#comments</comments>
		<pubDate>Mon, 04 Jan 2010 15:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>
		<category><![CDATA[scm]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
Table of Contents
    * Feature Development
    * Bug Fixes
    * QA Branch Management
    * Production Tagging
    * Summary
    * Notes
(Link: ReinH — A Git Workflow for Agile Teams)
]]></description>
			<content:encoded><![CDATA[<p>
Table of Contents<br />
    * Feature Development<br />
    * Bug Fixes<br />
    * QA Branch Management<br />
    * Production Tagging<br />
    * Summary<br />
    * Notes<br />
(Link: <a class="deliciouslink" href="http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html" title="ReinH — A Git Workflow for Agile Teams" target="_blank">ReinH — A Git Workflow for Agile Teams</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2010/01/04/links9/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>git-wtf &#8211; displays the state of your repository in a readable, easy-to-scan format</title>
		<link>http://www.sordyl.info/2009/12/07/links2/</link>
		<comments>http://www.sordyl.info/2009/12/07/links2/#comments</comments>
		<pubDate>Mon, 07 Dec 2009 16:00:04 +0000</pubDate>
		<dc:creator>BrentSordyl</dc:creator>
				<category><![CDATA[git]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[
git-wtf displays the state of your repository in a readable, easy-to-scan format. It&#8217;s useful for getting a summary of how a branch relates to a remote server, and for wrangling many topic branches. git-wtf can show you: &#8211; How a branch relates to the remote repo, if it&#8217;s a tracking branch. &#8211; How a branch [...]]]></description>
			<content:encoded><![CDATA[<p>
git-wtf displays the state of your repository in a readable, easy-to-scan format. It&#8217;s useful for getting a summary of how a branch relates to a remote server, and for wrangling many topic branches. git-wtf can show you: &#8211; How a branch relates to the remote repo, if it&#8217;s a tracking branch. &#8211; How a branch relates to integration branches, if it&#8217;s a feature branch. &#8211; How a branch relates to the feature branches, if it&#8217;s an integration branch.<br />
(Link: <a class="deliciouslink" href="http://git-wt-commit.rubyforge.org/git-wtf" title="git-wtf - displays the state of your repository in a readable, easy-to-scan format" target="_blank">git-wtf &#8211; displays the state of your repository in a readable, easy-to-scan format</a>)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sordyl.info/2009/12/07/links2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
