You need to sign in or sign up before continuing.
Take a photo of a barcode or cover
4.07 AVERAGE
4.07 AVERAGE
Mostly, reads as a "why Git is the best" thesis.
Not the best/clearest technical documentation I've ever read.
Some interesting tidbits to index in the back of my mind.
Not the best/clearest technical documentation I've ever read.
Some interesting tidbits to index in the back of my mind.
I've picked up a couple of tricks from this book, and I feel I understand Git much better than I used to, but I'm not entirely sure how useful this knowledge is going to be. I guess even though I now understand Git, I still hope that it will get replaced by something easier to use in the near future. It's a fool's hope, but there it is. In either case, I enjoyed the book a lot, and would recommend it to other people who wanted to learn more about Git.
A reasonably clear introduction and explanation of git. The first part does a good job at explaining things for new users, and is especially good at pointing out saner ways to do things that were added in recent versions of git. It seemed to cover most of the stuff I've learned the hard way, and I found one or two new things. The only glaring omission is it didn't seem to cover git reset at all.
The chapter on managing a project with git covered problems I'm just starting to encounter, so was appreciated. The section on subprojects showed all their many warts; candor appreciated. The coverage of subtree merging was entirely new to me and very interesting to see. The final chapter on internals does a good job of really getting down and dirty at both the git database and wire protocol levels.
The only things I didn't like were some slightly shady bits of sysadmin advice. In at least two places the user is advised to set up things in an insecure way. (I hope to get these corrected.) In other places the user is walked through cloning a project from git and manually installing it -- even though apt-get is used to install other things on sometimes the same page.
The chapter on managing a project with git covered problems I'm just starting to encounter, so was appreciated. The section on subprojects showed all their many warts; candor appreciated. The coverage of subtree merging was entirely new to me and very interesting to see. The final chapter on internals does a good job of really getting down and dirty at both the git database and wire protocol levels.
The only things I didn't like were some slightly shady bits of sysadmin advice. In at least two places the user is advised to set up things in an insecure way. (I hope to get these corrected.) In other places the user is walked through cloning a project from git and manually installing it -- even though apt-get is used to install other things on sometimes the same page.
I'm keeping this book nearby my desk. Yes, all this information can be piecemealed together via posts online, but having the whole picture makes understanding Git much easier.
The middle is a bit boring / not relevant for everybody.
While it doesn't read like a summer beach book, Pro Git does do a great job of explaining git's killer features. The graphics used to convey the branching/merging model drive the point home really well. Git's a game changer due to how it handles merging and branching. SVN made branching trivial and merging remained painful. Git solves the difficult merge problem by tracking tree changes and common ancestry well. The distributed nature of git can be a huge opportunity for new ways to organize and work as well.
Mostly, reads as a "why Git is the best" thesis.
Not the best/clearest technical documentation I've ever read.
Some interesting tidbits to index in the back of my mind.
Not the best/clearest technical documentation I've ever read.
Some interesting tidbits to index in the back of my mind.