This Post Has 9 Comments

1. Still One of the Best Git Intros Out There
   I’ve been using Git for about 15 months now, and have studied around 5 Git books, all of which have been helpful. But I would like to say this: this book is (to me) the one that expresses the technical aspects most precisely. I don’t know if it is because Travis simply UNDERSTANDS Git better than the other authors I read, or whether he simply expresses his ideas more precisely. I’ll wager both. Travis gets right to heart of each topic, including WHY and WHEN one would use one feature/option over another. Thank you, Travis for your excellent work in putting this one together. It makes me wish I had studied THIS book first — I think it would have gotten me off the launching pad with Git quicker. :-)**thumbs up**

   Reply

2. Detailed, Approachable, but Lacked some Detail
   This book was an excellent introduction to Git. The author went into good detail of the basic uses of Git and made it exciting to try it. I have referred to the book almost daily since reading it. I definitely recommend it for the average user. My only wish is that the book had gone into more detail of git’s administrative features.

   Reply

3. Well written, doesn’t cover enough
   It’s a decent book. It explained the basics really well, but something bothers me: It doesn’t cover applying patches! Not even in the reference! That this book doesn’t cover a heavily-used feature of git (in collaborative projects) is disappointing.”Pragmatic” doesn’t describe the depth of content, to me. It describes the manner in which the content is presented. The book could have been a bit thicker, with more complete feature coverage, and maintained its title.

   Reply

4. Very superficial, and does not cover collaboration
   I’ve enjoyed books published by The Pragmatic Programmers for years, and have both the CVS and SVN predecessors of this book, but Pragmatic Version Control Using Git is really a let down. The information is very superficial, and can be easily gleaned from the internet.I was looking for a book that would make suggestions on how to collaborate on my project using Git, after all, it is a distributed version control system, but the book doesn’t cover that. I finally found the Pro Git Book which is free and available online, and covers many models of collaboration.If you have no idea what version control is, this book might be helpful; otherwise, save your money.

   Reply

5. A pragmatic book as it title says
   Don’t expect to get all details of how git works or find more than an intro to the advanced features of git, because this book explains the basics and daily usage of git. I would still definitely suggest it because it does what it promises. And if you only want to understand how to use it in a daily basis, this book is for you.Of course, it is a discussion if it is right to learn things in a pragmatic way, or learn how it actually works. To learn how it actually works go to the manual or try a book like “Pro Git”.

   Reply

6. Great addition to the Pragmatic line of software books.
   I have the associated book Pragmatic Version Control Using Subversion by Mike Mason that is absolutely outstanding in terms of providing a working knowledge of the software in a readily comprehensible manner. This book on Using Git by Travis Swicegood continues that tradition. I am very happy with the purchase.

   Reply

7. Five Stars
   Fine book to whom wants to get to know GIt and use it.

   Reply

8. Great introduction to Git
   Using a modern version control system likely means a choice between Git and Mercurial, which are way ahead of the previous generation (which includes the very popular Subversion). Git is becoming more and more widely used, with lots of open source projects switching to it. Even though quite easy to use for basic things, it takes some effort to learn to master all its features.Pragmatic Version Control using Git provides most of the information needed, while also being a great starting point if you never used Git. It’s written in a tutorial-like fashion, where each topic is covered by through explanations and focused examples (also available for download).The first part covers Git configuration and very basic operations. The explanation is quite exhaustive, which is very important as it’s fundamental to understand the philosophical differences between Git and other software: Subversion, for instance, works quite differently but many folks still try to use Git as if it was Subversion with another name: this is quite a pity, as Git offers much more power and flexibility. This difference is clear when you see that half of the book (90 pages) is only devoted to working with local files, which means that with Git you mostly (even only, in some cases) work locally (compared to Subversion where most of the work involves a remote repository).The second part covers, besides some notions about how to work with remote repositories, the advanced topics (rewriting revision history, …). One of the interesting parts is the one which explains how to migrate from, or even interoperate with, Subversion and CVS repositories: very useful if you’re considering the switch to Git but you want it to be slow and without pain. Some useful notes on Gitosis (a Git repository manager) and other tools close the book.A quick reference to everything Pragmatic Version Control using Git explains is available in appendix A, and a single-page cheat sheet you can detach from the book is also provided. These are really welcome, as finding a particular thing in a tutorial-like book like this can be quite boring.This book is, all in all, a fine choice for learning Git. It might not be the best thing to use as a reference once you learned the topics, still it is acceptable even when used as such.

   Reply

9. This book is a good overview of GIT commands and how to use it for your day-to-day business. The very good point is that you are taken through a real (small) project that allows you to practice and understand the how and why quite easily.I would have liked a bit more information about project structure and organisation within the repository but I guess that GIt being so open to any structure, giving an example would restrict the field of possibilities.Easy to read and well written book. I recommend it for people that really have no idea on what Version Control tool to use and to people having to use GIT for the first time.The GUI 3rd party tools section needs an update – there are more options out since the book was written.

   Reply