Enter your mobile number or email address below and we'll send you a link to download the free Kindle Reading App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry.
> Shop now
Scott Chacon is the CIO and co-founder of GitHub Inc, the popular developer tool and code hosting service. Scott has been involved in the Git community for many years, compiling the Git Community Book, maintaining the main Git website and writing two early and popular books on learning Git, both of which are open sourced.
Scott writes and speaks around the world both about Git and about running and growing a startup company.
I began reading Pro Git, by Scott Chacon, after having already used Git in a large team-based project. Due to this, I was afraid I would get bored of the book very easily since I had already learned a decent amount of the material. This was most assuredly not the case. Chacon has done an excellent job in writing a book that serves as an excellent beginners guide and a quick reference at the same time.
The first part of the book is devoted to looking at multiple version control systems along with a history of version control. Chacon also makes it very easy to set Git up in a number of environments so that you can get started right away. The first half of the book is dedicated towards basics of the system, advanced features, such as rebasing, and setting up a remote server for git. The next half of the book contains a wealth of knowledge regarding best practices when using Git, additional tools and configuration options, and finally, nitty-gritty details on how Git works under the hood.
My biggest complaint would have to be the fact that the material on using Git remotely is scattered in a couple different parts of the book. This makes it slightly difficult to find specific information regarding remote work.
Overall, Chacon did an excellent job with Pro Git. After reading this book I was able to easily fill in the holes in my knowledge and felt significantly more comfortable maintaining a Git system for personal and team projects.
Was this review helpful to you?
i read through all the other git books to this date and i came to the conclusion that this is the best as far as visual explanations of the git concepts and methodology is concerned. my colleagues had the same "aha" experience as i after reading through this book, as we were all suffering from a not so clear picture of how git actually branches, merges and treats remote repositories. i can highly recommend it!
Was this review helpful to you?
Scott Chacon is one of the guys behind github -- a hosting site for projects managed by Git distributed version control system. As such, Scott is extremely competent in all things Git, and he wrote a book (or should I say the book) on Git. The book is called Pro Git. I've been using Git for some time now, so I couldn't wait to get my hands on a printed copy of the book. (I'm old-fashioned that way -- I prefer reading paper books.)
Pro Git is published by Apress. On 250 odd pages, Scott manages to bring Git across in a very vivid way. Lots of sample sessions and a huge number of figures make Git come alive and fun to use! (Only at one point while reading the book, did I think: "why is he telling me that?", but it can't have been too bad, because upon writing this, I can't find the place.)
Pro Git starts off easily enough, but it does so at a fast pace, for which I was grateful: you get past the basics on page 45, which means the book gets you set up quickly, so that you can start taking Git for a spin.
Chapter 3 is called "Git Branching", and the thirty pages explain all you ever wanted to know (as well as all you never wanted to know ) about branching. This part is hardcore, but Scott explains this with lots of diagrams, making it easier for us to follow.
One of the best chapters in the book, for me, is called "Git on the server". Scott explains the different methods of setting up Git so as to be able to collaborate.
If you use Git or intend to (and I'd certainly recommend you look at it), I very warmly recommend Scott Chacon's Pro Git: it's the best companion you'll have for Git.
I just recently switched to Git after being a longtime user of other SCM tools. I had no previous knowledge of Git, and purchased this book as a reference to help me understand how Git is different from SVN/CVS/TFS and to help me decide if I was going to switch. I picked two books here on Git (the O'Reilly book being the other) and dove in headfirst.
All of the routine tasks, commands and options are well covered here. Covered topics include all of the required basics, using remote repositories, staging, branching strategies and so on.
I'm a really visual person and I really like diagrams. I was quickly able to understand the key strengths of Git by looking at the included diagrams in a way that just reading some text does not convey.
It really bothers me that someone would put in so much effort to write a comprehensive Git book and not include a summary of the Git commands and what each one does. I read this book, like a book - I started at the beginning and read it through. It's a very informative book that details why, when, and how to use many git commands. Now, I want to refer to the book - but the git commands are scattered all over the book. When I want to look up a git command it's likely discussed in multiple places in the book, I have to flip around to dig out the a comprehensive picture of the command.
This book would really be helped by a chapter or appendix that covers *all* of the git commands. I use 'git help' - that's information that should be in this book. I can't be a 'Pro' unless I know all of the commands.