Has anyone read Apress's Pro Git by Scott Chacon? Do you recommend it?
Git Tutorials for Beginners
11–20 of 29 posts
Re: Git Tutorials for Beginners
#12Why would anyone want 10 tutorials?
Re: Git Tutorials for Beginners
#13Has anyone read Apress's Pro Git by Scott Chacon? Do you recommend it?
I also recommend to heavily use gitk while learning, just use it to see what happens after you do something in your test repositories. It's very enlightening.
Re: Git Tutorials for Beginners
#14http://people.gnome.org/~newren/eg/
easygit is git with sane defaults and better error messages. It uses real git commands, so you don't need to unlearn anything when graduating to git. It has extra sanity checks (like checking for unstaged changes when committing). The help messages are more verbose and use more consistent terminology than git's man pages. For example, easygit always uses the term "staged" instead of "index/staged/add/hard/soft/mixed/cached/HEAD/etc." And `eg revert` behaves the same as Perforce, SVN, and Mercurial revert.
Re: Git Tutorials for Beginners
#15Re: Git Tutorials for Beginners
#16A similar list for Mercurial, please?
Re: Git Tutorials for Beginners
#17Re: Git Tutorials for Beginners
#18Beyond git tutorials, I recommend easygit (eg). It's a "training wheels" wrapper for git and available in Ubuntu's Package Manager. http://people.gnome.org/~newren/eg/ easygit is git with sane defaults and better error messages. It uses real git commands, so you don't need to unlearn anything when graduating to git. It has extra sanity checks (like checking for unstaged changes when committing). The help messages are…
Re: Git Tutorials for Beginners
#19Re: Git Tutorials for Beginners
#20Beyond git tutorials, I recommend easygit (eg). It's a "training wheels" wrapper for git and available in Ubuntu's Package Manager. http://people.gnome.org/~newren/eg/ easygit is git with sane defaults and better error messages. It uses real git commands, so you don't need to unlearn anything when graduating to git. It has extra sanity checks (like checking for unstaged changes when committing). The help messages are…
The overloading of "checkout" to mean revert a file as well as "switch to a different branch" is for me one of the most confusing git design choices.