<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Git</title>
	<link>http://micheljansen.org/blog/entry/482</link>
	<description>My Exhaust To The Web</description>
	<pubDate>Tue, 06 Jan 2009 22:15:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Michel&#8217;s Exhaust &#187; Reverting changes in Git</title>
		<link>http://micheljansen.org/blog/entry/482#comment-90372</link>
		<author>Michel&#8217;s Exhaust &#187; Reverting changes in Git</author>
		<pubDate>Wed, 20 Aug 2008 13:34:40 +0000</pubDate>
		<guid>http://micheljansen.org/blog/entry/482#comment-90372</guid>
		<description>[...] Exhaust        Currently:             &#171; Git      Reverting changes in [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Exhaust        Currently:             &#171; Git      Reverting changes in [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michel</title>
		<link>http://micheljansen.org/blog/entry/482#comment-85473</link>
		<author>Michel</author>
		<pubDate>Wed, 06 Aug 2008 11:56:22 +0000</pubDate>
		<guid>http://micheljansen.org/blog/entry/482#comment-85473</guid>
		<description>The main difference is that there is essentially no main server; at least not necessarily. You can push and pull to and from any git repository without losing any history. You always have a local repository containing all the history and when you push the changes to a central server (it is possible to have one) you push all the commits you did locally, not just the current state the project is in.

Of course, it's still a SCM, so in many ways it's similar to subversion. It has some cool extra features like the ability to "cherry pick" changes from a single commit from someone else's branch, for instance a bugfix. It's also apparantly better at resolving conflicts and keeping the repository sane, but I don't really have any personal experience on that end yet.</description>
		<content:encoded><![CDATA[<p>The main difference is that there is essentially no main server; at least not necessarily. You can push and pull to and from any git repository without losing any history. You always have a local repository containing all the history and when you push the changes to a central server (it is possible to have one) you push all the commits you did locally, not just the current state the project is in.</p>
<p>Of course, it&#8217;s still a SCM, so in many ways it&#8217;s similar to subversion. It has some cool extra features like the ability to &#8220;cherry pick&#8221; changes from a single commit from someone else&#8217;s branch, for instance a bugfix. It&#8217;s also apparantly better at resolving conflicts and keeping the repository sane, but I don&#8217;t really have any personal experience on that end yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remko</title>
		<link>http://micheljansen.org/blog/entry/482#comment-85437</link>
		<author>Remko</author>
		<pubDate>Wed, 06 Aug 2008 09:55:18 +0000</pubDate>
		<guid>http://micheljansen.org/blog/entry/482#comment-85437</guid>
		<description>So the main difference with subversion is that you can commit locally? In other words: You create some kind of local snapshots during your daily work. Besides that it sound really similar.  
And another question: Does it keep your history of changes locally when you have committed to the server? Or are all of these changes synchronized with the host system?</description>
		<content:encoded><![CDATA[<p>So the main difference with subversion is that you can commit locally? In other words: You create some kind of local snapshots during your daily work. Besides that it sound really similar.<br />
And another question: Does it keep your history of changes locally when you have committed to the server? Or are all of these changes synchronized with the host system?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
