Pro Git 2nd Edition, Kindle Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Enter your mobile number or email address below and we'll send you a link to download the free Kindle 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 mobile phone number.
What other items do customers buy after viewing this item?
Would you like to tell us about a lower price?
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
That said, as another reviewer has pointed out, there are some rather confusing statements scattered here and there. Because the authors were too familiar with the material, they didn't see certain ambiguities they were injecting into the text. These probably won't get fixed unless someone takes careful notes as they go, and submits the whole set back upstream.
Another problem is that there was some sloppiness in editing this second edition of the book. Occasionally, some example commands are left out. Or some object labeling is clearly wrong in the text. Or some figure is reprinted a second time over a different caption instead of the correct figure being included for that second caption. The thing to know is that when you encounter these situations, you can go on-line and download the current PDF copy into your browser, and look there for the corrected presentation. Yes, this process is somewhat annoying, but if I had to weigh the overall effect, I still prefer a printed copy for the initial long read-through to learn the tool.
I decided to read this whole book even though I'm just a newbie just so I had an idea of the breadth of topics and different features. I'll be sticking with basic usage but I can go back and reference the advanced topics later. I did skim read some of those topics, no need to read advanced scripts when I won't be using those.
The main take out for me for the advantages of git are:
- ability to save all your work in a logical manner (in topic branches) before you do any commit. There is no good solution to this in the tools I'm used to except for a manual save to a network drive or offline storage
- flexible workflow - there are many many ways to set up your workflow, including code review, integration, qa and many other steps you may or may not want
- let you use github, a great way to backup and share your work, more likely for personal projects but could also be great for company use in some cases
- the inner workings are completely exposed so you have the power to do many custom workflows, enforcement of particular policies and so on
- bundling of commits into logical groupings with options and many options for handling these well
- great tools for finding out why some code went wrong, pinpointing which check in or which tag created the fault
Changing from a traditional tool to git would be a major undertaking but well worth the effort.
This book has given me so many reasons to hold git high above all other version control systems.