>> Seconded. Worth the $9 to save the time spent trawling through bad >> blog posts for similar info! As far as I can tell, this is also >> pretty >> much the only resource to have if you want to do more than just >> "human- >> oriented" version control using Git. > > Are you two implying that there is no free documentation for git?
No. There is plenty of documentation for git -- the man pages are good, and the Git docs[1] are also useful. However, the Peepcode PDF, 121 pages of diagrams and clear text, certainly beats the brief Git for Computer Scientists[2], and also includes clear descriptions of typical workflow steps, installation, etc. (not relevant in my case, but still useful to have in one place). I'm happy to pay $9 for that. > That goes against the spirit of open source, wouldn't you say, if > the docs > are all proprietary? The docs produced by the Git project aren't proprietary: there are plenty at [1], not to mention `man git`. I just see a great deal of value in clear, explanatory text as produced by accomplished technical writers. If the Peepcode PDF saves me five minutes, it was worth the money. I don't think a discussion of the spirit of open source is particularly relevant to this forum, so I shan't address that point. -R [1] <http://git-scm.com/documentation> [2] <http://eagain.net/articles/git-for-computer-scientists/> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
