I've just started reading it. And, so far, it is also very helpful. Did a wonderful explanation about "git mv" to be able to restructure your project's files into different subdirectories and why it is so simple and fast. I have a much better idea how git is "content addressable" and how different it is from other VCS's methods of tracking changes. Pro-Git was also fairly good at it. Leave it to Linus to come at VCS "sideways". Also liked the explanation of where the name "git" came from. That's not a Texan slang word. I like have two different references. It's like reading different Bible translations. I get a better idea of meaning due to the different viewpoints.
On Thursday, November 29, 2012 1:22:45 PM UTC-6, Thom Parkin wrote: > > This review makes it look like a great book. Even with the few caveats. > I found Pro-Git to be indispensable as a teacher initially and now as a > reference (for those functions I use less often - there are so very many of > them). > > Thanks for sharing this!! > > Thom > ====== > If DEBUGGING is the process of removing errors > Then PROGRAMMING must be the process of inserting them! > > On Monday, November 26, 2012 3:47:45 PM UTC-5, John McKown wrote: >> >> >> This is on "Version Control With Git, 2nd Edition". I read the review and >> decided to get the Kindle version of the book for just under US $16.00 . >> But the Kindle is at home, so I can't look at it right now. I've just about >> finished up "Pro Git" and liked it. I am a bit off in the head, in that I >> like to read well written computer documentation. OK, maybe some other ways >> too. <grin/> >> >> >> http://books.slashdot.org/story/12/11/26/1330226/book-review-version-control-with-git-2nd-edition >> > --