<story><title>Git in six hundred words</title><url>http://maryrosecook.com/blog/post/git-in-six-hundred-words</url></story><parent_chain><item><author>NelsonMinar</author><text>&amp;quot;You go to commit some code to a public repo. The maintainer scolds you for using merges instead of fast forwards.&amp;quot;&lt;p&gt;&amp;quot;You decide to bring in some more code from the public repo. Here is a 6000 word essay on what rebase means.&amp;quot;&lt;p&gt;&amp;quot;You try to look at an old version of the code. Suddenly you are in ‘detached HEAD’ state. The End.&amp;quot;&lt;p&gt;I love git, but simple intros like this hide all the confusing complexity and awkward UI that quickly comes to the forefront when using git for everyday work.</text></item></parent_chain><comment><author>reuven</author><text>I teach courses on Git, and I couldn&amp;#x27;t agree more.  &lt;i&gt;Many&lt;/i&gt; of my students have been told that Git is simple, and they just need to know 10 commands.  Or they can think about it like SVN.  Or that they should push, pull, and that&amp;#x27;s about it.&lt;p&gt;Which has the effect of (a) making them fear Git, (b) making them feel like they&amp;#x27;ll never figure it out, (c) and convincing them that they&amp;#x27;re always on the verge of losing data.  I&amp;#x27;ve literally had students at the start of my course refer to Git as &amp;quot;that system that makes me lose files.&amp;quot;&lt;p&gt;Once I teach people about Git&amp;#x27;s objects and data structures, things suddenly become much more obvious to these people. Git becomes less of a mystery.&lt;p&gt;I&amp;#x27;m not saying that Git is easy for people to understand or use, because it isn&amp;#x27;t.  It has a steep learning curve -- one which I think is worth the effort.  But I think that it does a disservice to Git newbies to try to summarize all of Git&amp;#x27;s functionality in a short essay, and then proclaim, &amp;quot;See?  There&amp;#x27;s not that much to learn here!&amp;quot;</text></comment>
<story><title>Git in six hundred words</title><url>http://maryrosecook.com/blog/post/git-in-six-hundred-words</url></story><parent_chain><item><author>NelsonMinar</author><text>&amp;quot;You go to commit some code to a public repo. The maintainer scolds you for using merges instead of fast forwards.&amp;quot;&lt;p&gt;&amp;quot;You decide to bring in some more code from the public repo. Here is a 6000 word essay on what rebase means.&amp;quot;&lt;p&gt;&amp;quot;You try to look at an old version of the code. Suddenly you are in ‘detached HEAD’ state. The End.&amp;quot;&lt;p&gt;I love git, but simple intros like this hide all the confusing complexity and awkward UI that quickly comes to the forefront when using git for everyday work.</text></item></parent_chain><comment><author>davidgerard</author><text>+1. I want an intro to git that covers &lt;i&gt;all the weird confusing shit newbies meet&lt;/i&gt;. I think I&amp;#x27;ve read enough of the travel brochure version.</text></comment>