What a great idea. Will future updates be available as well? Perhaps in a DVCS for easy access?<p>I'd be a happy man if ALL tech books lived in a DVCS. Users could fork it, push updates, fixes, etc. and the author could integrate changes as they see fit. No more searching for errata URLs, simply update your repository.<p>I'd even pay for this.<p>A great example of where this idea could be really useful is with Linux books like 'Linux Device Drivers', or 'Understanding the Linux Kernel'. These books are often out of date at the time they're published. I'd happily pay for access to them in a repository somewhere.<p>This is not unlike how the Pragmatic Bookshelf (<a href="http://pragprog.com/)works" rel="nofollow">http://pragprog.com/)works</a> today with the exception that you have to wait for new book versions to become available, then regenerate them in your e-version format of choice. It'd be much more useful if the community of users could contribute back to the book source repository at their leisure.
I'd love to request a copy, but the District of Columbia is not an option in the state field. I know we're not technically a state, but we're still people!<p>I actually have this problem more often than I should. It is especially painful when I'm trying to <i>pay</i> for a product. Tip to all web developers: Make sure DC is an option in your signup/order forms.
> Heck, people often pay more per click on AdWords than it costs to print and ship a book.<p>Wow. Such a great way to spend money, and I think it would get them some great ROI.<p>(They are launching their new SCM veracity.)
I reside in India.
My request went through without a hitch (Opera11.50/Linux).<p>I think this is great idea for a version control book.
I work in a dual-vcs environment (Hg, git - Work, personal)
Really great idea. I checked out the ToC before ordering and I like the way it offers a comparison of the major existing version control systems and then includes in the comparison at the end the new version control system. So basically it's useful to anyone who is thinking about moving to a new VCS and "happens to mention" the author's VCS. I'd pay for that any day, but instead I'll just recommend the book to everybody I know... which is probably what they want...
I picked up a copy of this book at OSCON a few weeks ago. It's well-written, humorous, and a great overview of Mercurial and Git and a good introduction to Veracity.<p>If you have been using Mercurial or Git for a while, there won't be much new in here, but it is an enjoyable and quick read. And it could come in handy for converting those holdouts on your team still using Subversion (or, like a few people I work with, no version control at all!).
Fantastic! Thanks for doing this because some of our devs barely use SVN in my office and it would be great if they became more aware of the benefits of version control. I've used git on previous projects and love the distributed model, hopefully having this as a good reading option in our office will help improve us all.
Smart Bear does the same thing: <a href="http://smartbear.com/best-kept-secrets-of-peer-code-review/" rel="nofollow">http://smartbear.com/best-kept-secrets-of-peer-code-review/</a> - I received a free (paper) book after attending a session about peer code review.<p>I still haven't read the book, but that's a whole different discussion.
My request went through (Philippines) :) I hope it comes. I'd like to show my workmates the beauty of version control and what they're missing.<p>There's a free online version (also PDF) <a href="http://www.ericsink.com/vcbe/index.html" rel="nofollow">http://www.ericsink.com/vcbe/index.html</a>
It's worth mentioning that you can also read the book for free online: <a href="http://www.ericsink.com/vcbe/index.html" rel="nofollow">http://www.ericsink.com/vcbe/index.html</a><p>Take a look and decide if it's something you like to have in paper form.
Looks like an interesting book. Were you taken to another page when clicking "Request a book"? For me, the page was reloaded and my answers to questions 1-8 were deselected.
I submitted twice using different browsers and both times the form came back empty except for the address. No sign of any error or missing fields. The PDF will be then.
The author donated an entire box (!) of this book to our students. The book itself is well-written, which is surprising considering that it appears aimed at selling people on Veracity. But, to be fair, after comparing Veracity to Perforce, I am sold on Veracity too. :3<p>Even if you don't care about enterprisy VCS, this book covers three established community-based VCSes in a really great way. Get a copy, put it on your shelf, give it a read.