• Complain

Bryan OSullivan - Mercurial: The Definitive Guide

Here you can read online Bryan OSullivan - Mercurial: The Definitive Guide full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. year: 2009, genre: Computer. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

No cover
  • Book:
    Mercurial: The Definitive Guide
  • Author:
  • Genre:
  • Year:
    2009
  • Rating:
    5 / 5
  • Favourites:
    Add to favourites
  • Your mark:
    • 100
    • 1
    • 2
    • 3
    • 4
    • 5

Mercurial: The Definitive Guide: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "Mercurial: The Definitive Guide" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

Bryan OSullivan: author's other books


Who wrote Mercurial: The Definitive Guide? Find out the surname, the name of the author of the book and a list of all author's works by series.

Mercurial: The Definitive Guide — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "Mercurial: The Definitive Guide" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Mercurial: The Definitive Guide
Compiled from 93154fbaae9b (2009-10-27)
Bryan O'Sullivan

Copyright 2006, 2007, 2008, 2009 Bryan O'Sullivan


Preface
Technical storytelling

A few years ago, when I wanted to explain why I believed that distributed revision control is important, the field was then so new that there was almost no published literature to refer people to.

Although at that time I spent some time working on the internals of Mercurial itself, I switched to writing this book because that seemed like the most effective way to help the software to reach a wide audience, along with the idea that revision control ought to be distributed in nature. I publish the book online under a liberal license for the same reason: to get the word out.

There's a familiar rhythm to a good software book that closely resembles telling a story: What is this thing? Why does it matter? How will it help me? How do I use it? In this book, I try to answer those questions for distributed revision control in general, and for Mercurial in particular.

Thank you for supporting Mercurial

By purchasing a copy of this book, you are supporting the continued development and freedom of Mercurial in particular, and of open source and free software in general. O'Reilly Media and I are donating my royalties on the sales of this book to the Software Freedom Conservancy (http://www.softwarefreedom.org/) which provides clerical and legal support to Mercurial and a number of other prominent and worthy open source software projects.

Acknowledgments

This book would not exist were it not for the efforts of Matt Mackall, the author and project lead of Mercurial. He is ably assisted by hundreds of volunteer contributors across the world.

My children, Cian and Ruairi, always stood ready to help me to unwind with wonderful, madcap little-boy games. I'd also like to thank my ex-wife, Shannon, for her support.

My colleagues and friends provided help and support in innumerable ways. This list of people is necessarily very incomplete: Stephen Hahn, Karyn Ritter, Bonnie Corwin, James Vasile, Matt Norwood, Eben Moglen, Bradley Kuhn, Robert Walsh, Jeremy Fitzhardinge, Rachel Chalmers.

I developed this book in the open, posting drafts of chapters to the book web site as I completed them. Readers then submitted feedback using a web application that I developed. By the time I finished writing the book, more than 100 people had submitted comments, an amazing number considering that the comment system was live for only about two months towards the end of the writing process.

I would particularly like to recognize the following people, who between them contributed over a third of the total number of comments. I would like to thank them for their care and effort in providing so much detailed feedback.

Martin Geisler, Damien Cassou, Alexey Bakhirkin, Till Plewe, Dan Himes, Paul Sargent, Gokberk Hamurcu, Matthijs van der Vleuten, Michael Chermside, John Mulligan, Jordi Fita, Jon Parise.

I also want to acknowledge the help of the many people who caught errors and provided helpful suggestions throughout the book.

Jeremy W. Sherman, Brian Mearns, Vincent Furia, Iwan Luijks, Billy Edwards, Andreas Sliwka, Pawe Soyga, Eric Hanchrow, Steve Nicolai, Micha Masowski, Kevin Fitch, Johan Holmberg, Hal Wine, Volker Simonis, Thomas P Jakobsen, Ted Stresen-Reuter, Stephen Rasku, Raphael Das Gupta, Ned Batchelder, Lou Keeble, Li Linxiao, Kao Cardoso Flix, Joseph Wecker, Jon Prescot, Jon Maken, John Yeary, Jason Harris, Geoffrey Zheng, Fredrik Jonson, Ed Davies, David Zumbrunnen, David Mercer, David Cabana, Ben Karel, Alan Franzoni, Yousry Abdallah, Whitney Young, Vinay Sajip, Tom Towle, Tim Ottinger, Thomas Schraitle, Tero Saarni, Ted Mielczarek, Svetoslav Agafonkin, Shaun Rowland, Rocco Rutte, Polo-Francois Poli, Philip Jenvey, Petr Tesak, Peter R. Annema, Paul Bonser, Olivier Scherler, Olivier Fournier, Nick Parker, Nick Fabry, Nicholas Guarracino, Mike Driscoll, Mike Coleman, Mietek Bk, Michael Maloney, Lszl Nagy, Kent Johnson, Julio Nobrega, Jord Fita, Jonathan March, Jonas Nockert, Jim Tittsler, Jeduan Cornejo Legorreta, Jan Larres, James Murphy, Henri Wiechers, Hagen Mbius, Gbor Farkas, Fabien Engels, Evert Rol, Evan Willms, Eduardo Felipe Castegnaro, Dennis Decker Jensen, Deniz Dogan, David Smith, Daed Lee, Christine Slotty, Charles Merriam, Guillaume Catto, Brian Dorsey, Bob Nystrom, Benoit Boissinot, Avi Rosenschein, Andrew Watts, Andrew Donkin, Alexey Rodriguez, Ahmed Chaudhary.

Conventions Used in This Book

The following typographical conventions are used in this book:

Italic

Indicates new terms, URLs, email addresses, filenames, and file extensions.

Constant width

Used for program listings, as well as within paragraphs to refer to program elements such as variable or function names, databases, data types, environment variables, statements, and keywords.

Constant width bold

Shows commands or other text that should be typed literally by the user.

Constant width italic

Shows text that should be replaced with user-supplied values or by values determined by context.

Tip

This icon signifies a tip, suggestion, or generalnote.

Caution

This icon indicates a warning or caution.

Using Code Examples

This book is here to help you get your job done. In general, you may use the code in this book in your programs and documentation. You do not need to contact us for permission unless youre reproducing a significant portion of the code. For example, writing a program that uses several chunks of code from this book does not require permission. Selling or distributing a CD-ROM of examples from OReilly books does require permission. Answering a question by citing this book and quoting example code does not require permission. Incorporating a significant amount of example code from this book into your products documentation does require permission.

We appreciate, but do not require, attribution. An attribution usually includes the title, author, publisher, and ISBN. For example: Book Title by Some Author. Copyright 2008 OReilly Media, Inc., 978-0-596-xxxx-x.

>.

Safari Books Online
Note

When you see a Safari Books Online icon on the cover ofyour favorite technology book, that means the book isavailable online through the OReilly Network SafariBookshelf.

Safari offers a solution thats better than e-books. Its a virtual library that lets you easily search thousands of top tech books, cut and paste code samples, download chapters, and find quick answers when you need the most accurate, current information. Try it for free at http://my.safaribooksonline.com.

How to Contact Us

Please address comments and questions concerning this book to the publisher:

OReilly Media, Inc.
1005 Gravenstein Highway North
Sebastopol, CA 95472
800-998-9938 (in the United States or Canada)
707-829-0515 (international or local)
707 829-0104 (fax)

We have a web page for this book, where we list errata, examples, and any additional information. You can access this page at:

http://www.oreilly.com/catalog/

Dont forget to update the attribute, too.

To comment or ask technical questions about this book, send email to:

<>

For more information about our books, conferences, Resource Centers, and the OReilly Network, see our web site at:

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «Mercurial: The Definitive Guide»

Look at similar books to Mercurial: The Definitive Guide. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «Mercurial: The Definitive Guide»

Discussion, reviews of the book Mercurial: The Definitive Guide and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.