GitHub

[Michael G Schwern]

Shlomi Fish wrote:
> This is just a tiny example. I also had many problems with "git checkout" and
> "git diff" no longer showing the diff for files that were "git add"'ed and 
> other aspects. 
> 
> Maybe I should read a good git tutorial or a document explaining its 
> architecture, but so far I found git hard-to-understand, poorly documented, 
> and counter-intuitive. I didn't have such problems with Subversion, which 
> always worked as I expected and was properly documented and intuitive.

You're right on all counts, but the overriding factor is that there's lots of
things that SVN makes painful or near impossible (merging branches,
obliterating changes, changing history, cherry-picking changes, branch
security, mirroring...) that git makes possible.  It's worth slogging through
the first month of utter conceptual confusion.

To that end, I found these immensely helpful:

SVN commands and their equivalent git commands side by side.  This is your
life preserver when you're floundering.
http://git.or.cz/course/svn.html

This blog post explaining the index, a staging area for your commit.  Once you
understand the index things will become much clearer.  Then you will know why
added things no longer show up in your diffs.
http://tomayko.com/writings/the-thing-about-git

It's worth going through the "Git Concepts" section of the user manual to
learn about how git stores things, because storage details get exposed to the
user.
http://www.kernel.org/pub/software/scm/git/docs/v1.6.3/user-manual.html#git-concepts

Finally, I've found just googling for random git blog posts to be very helpful.


-- 
100. Claymore mines are not filled with yummy candy, and it is wrong
     to tell new soldiers that they are.
    -- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
           http://skippyslist.com/list/