Rating:
(8 reviews)
Author: Visit Amazon's Richard E. Silverman Page
ISBN : 1449325866
New from $11.57
Format: PDF, EPUB
Download electronic versions of selected books Free Git Pocket Guide for everyone book 4shared, mediafire, hotfile, and mirror link
About the Author
Richard E. Silverman has a B.A. in computer science and an M.A. in pure mathematics. Richard has worked in the fields of networking, formal methods in software development, public-key infrastructure, routing security, and Unix systems administration. He co-authored the SSH, The Secure Shell: The Definitive Guide, 2e and the Linux Security Cookbook.
Books with free ebook downloads available Free Git Pocket Guide Paperback
- Paperback: 234 pages
- Publisher: O'Reilly Media (July 30, 2013)
- Language: English
- ISBN-10: 1449325866
- ISBN-13: 978-1449325862
- Product Dimensions: 4.2 x 7 inches
- Shipping Weight: 6.4 ounces (View shipping rates and policies)
Free Git Pocket Guide
Switching to Git after years using SVN, I had trouble finding my way around the new environment even though I only need pretty basic source control. I didn't "get it", and things that should have been easy were difficult.
Two earlier books, both acknowledged by Mr. Silverman in his preface, helped, but in striving for completeness they both obscured the basic instruction I needed in an enormous wealth of detail.
A "pocket guide" seemed just the ticket, and the author's intent, stated in the preface, showed a lot of promise:
"The primary goal of this book is to provide a compact, readable introduction to Git for the new user, as well as a reference to common commands and procedures that will continue to be useful once you've already gotten some Git under your belt."
He accomplished his goal by half, I think. Although compact and readable, the book suffers (mildly) from a lack of clarity that, for me, prevents its use as a reference. Take this:
"If the current branch is tracking an upstream in that remote, Git then tries to reconcile the current state of your branch with that of the newly updated tracking branch. If only you or the upstream has added commits to this branch since your last pull, then this will succeed with a "fast-forward" update: one branch head just moves forward along the branch to catch up with the other."
There's nothing wrong with that paragraph in terms of narrative flow, but if you try to use it as instruction you notice it has a lot of subjects taking action -- "the current branch", "Git", "you", "the upstream", "this", "one branch head" -- and among all those actors doing things it's hard to sort out what YOU need to do in order to make something happen.