Customer Reviews

Pro Git

5 star:		(26)
4 star:		(9)
3 star:		(1)
2 star:		(0)
1 star:		(0)

 

 

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!

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.

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 am a web developer working remotely. I am used to work with Subversion, but wanted to learn Git. The guides and tutorials I found in the web were either too simple or too complex. Until I found the online version of "Pro Git". After being delighted with the first two chapters, and tired of reading on screen, I decided to buy the book. And I am very happy with it!

This book provided the information I wanted, in a perfect rythm - Scott does not waste our time - he provides useful information on every page, and his explanations are extremely well written. Thanks a lot!

Also, the topics and their order are perfect. In chapter 1 and 2, only 45 pages, you learn to use Git, as you may already use Subversion. Chapter 3 is brilliant - it is where Scott explains Git branching - how it works and how you use it. It is also where the power of Git is revealed - and why you should change your version control system to it, if you can.

All the "mistery" terms around Git, like "origin", "master", "push", "pull", "remote", "rebase" are not misterious anymore. You are able to understand their meaning, and not only how to use the commands, but also why, and all the "logic" involved.

Git helps us to do complex things in simple ways - this complexity requires some learning. It is not like software that you can use reading "man" page or a simple tutorial. The "Pro Git" book is a very good resource to get up and running with Git, knowing and understanding very well what you are doing.

I thank the author and recommend this book.

This book succeeds at getting you ready to actually use git in your daily work. It's not a regurgitation of the online docs; it's not a developer's guide written to impress you with the elegance of the implementation. Its main focus is to give the reader practical tips on deploying git in various scenarios. I was familiar with git from having read the O'Reilly book and dabbling a bit, but Pro Git really helped me get over the "activation barrier" and start using it in my own projects.

There are many good tutorials on basic usage of Git but this was the book that taught me the best practices and important workflows which can be employed while using Git. Some parts of the book seem pretty advanced for daily use but the author's grasp of the subject and more important than that his style of explaining most of the difficult concepts proved to be very handy for me. Previously I used CVS and then Subversion for some projects and I started to use Git only a few months ago and now I really ask myself why I didn't read the book as soon as I started to use Git. It would make things much easier for me. Shortly, I sincerely advise this book to any developer who plans to work with Git (it will be especially useful if you're developing an open source project or plan to contribute to a popular one).

I was using the online version of this book for quite some time to get started with Git. However, having a hard copy and reading it front to back gave me a lot of new insights. On screen you just don't read with the same attention. The book is easy to read and it only takes a few hours to go through it.
I wish more technical books would be written like this.

Disclaimer: When I first read this book (almost a year ago), I was a complete beginner with Git. I now use Git on a daily basis and couldn't be a happier programmer.

You're probably asking yourself, "why is this guy writing a review on this book a year after he read it?". Well, I'm writing this review now because I still think about this book daily (and have a copy sitting on the front of my bookshelf). This is one of the best tech books (in general) that I've ever read.

When first reading this book, I had little to no experience with Git. I had heard about it numerous times from friends and colleagues, but never used it in a real sense. What originally motivated me to start learning about it was Github (probably the best website that was ever created for programmers).

After picking up a copy of Chacon's book, and transitioning myself from SVN -> Git, I found myself 'at home' with the Git ideals and methods used to handle version control. After a short period of time, using Git just became second nature, something that I had never experienced in my programming life.

As time has progressed and I've used Git more and more, I've become far more knowledgeable about version control in general, and actually have a far better understanding of source control and practices--something that I was never able to really have 'click' while using SVN or CVS.

Almost a year after my initial reading of 'Pro Git', I now write all software using Git, and couldn't live without it.

In short, buy this book and give Git a chance, you won't regret it. It is not only a life-changing version control system, but 'Pro Git' is an excellent resource to getting started simply, and helps you to really grasp what Git is all about, and why you need to start using it.

This is book easy and intuitive to understand.
I was exposed Git through CIT conference 4 months ago and I want to learn Git.

At the first time, I choose Version Control with Git: Powerful Tools and Techniques for Collaborative Software Development and it is hard to understand the concept of Git and merging/branching of Git.

I thought " Should I read one more time the Version Control with Git or buy another book?".
I choose this book and I am satisfied with my choice.

I realized that how books can be written differently for the same content(git).
If you are new to Git, I strongly recommend this book.

This book is perfect for someone who has a superficial understanding of Git, and wants to learn more.

Starting with basic use cases, logical steps are used to introduce advanced topics such as rebasing and submodules. The last chapter even dives into the contents of the .git directory and the formats of the files found there--including how to manipulate them using low-level commands. There are concise examples that show how use the git command line tool to accomplish each task, and illustrations help understand how each operation changes the state of the repository.

This book isn't the best introduction to version control in general, as the discussion of possible workflows is limited (doing all changes in feature-specific branches isn't the only approach), and it isn't made clear how Git distinguishes itself from other distributed version control systems such as Mercurial or Bazaar.