hgbook

diff en/mq.tex @ 3:906d9021f9e5

Making progress on autogenerated example output.
author Bryan O'Sullivan <bos@serpentine.com>
date Sat Jun 24 17:42:40 2006 -0700 (2006-06-24)
parents 379a802c0210
children 33a2e7b9978d
line diff
     1.1 --- a/en/mq.tex	Sat Jun 24 16:14:02 2006 -0700
     1.2 +++ b/en/mq.tex	Sat Jun 24 17:42:40 2006 -0700
     1.3 @@ -21,7 +21,7 @@
     1.4  
     1.5  The patch management problem arises in many situations.  Probably the
     1.6  most visible is that a user of an open source software project will
     1.7 -contribute a bugfix or new feature to the project's maintainers in the
     1.8 +contribute a bug fix or new feature to the project's maintainers in the
     1.9  form of a patch.
    1.10  
    1.11  Distributors of operating systems that include open source software
    1.12 @@ -35,7 +35,7 @@
    1.13  patch will contain only one bug fix (the patch might modify several
    1.14  files, but it's doing ``only one thing''), and you may have a number
    1.15  of such patches for different bugs you need fixed and local changes
    1.16 -you require.  In this situation, if you submit a bugfix patch to the
    1.17 +you require.  In this situation, if you submit a bug fix patch to the
    1.18  upstream maintainers of a package and they include your fix in a
    1.19  subsequent release, you can simply drop that single patch when you're
    1.20  updating to the newer release.
    1.21 @@ -99,7 +99,7 @@
    1.22  modifications those patches make.
    1.23  
    1.24  Quilt knows nothing about revision control tools, so it works equally
    1.25 -well on top of an unpacked tarball or a Suversion repository.
    1.26 +well on top of an unpacked tarball or a Subversion repository.
    1.27  
    1.28  \subsection{From patchwork quilt to Mercurial Queues}
    1.29  \label{sec:mq:quilt-mq}
    1.30 @@ -128,15 +128,19 @@
    1.31  \section{Getting started with Mercurial Queues}
    1.32  \label{sec:mq:start}
    1.33  
    1.34 -Because MQ is implemented as an extension, you have to explicitly
    1.35 -enable it in order to use it.  (You don't need to download anything;
    1.36 -MQ ships with the standard Mercurial distribution.)  To enable it,
    1.37 -edit your \filename{~/.hgrc} file, and add the following lines:
    1.38 +Because MQ is implemented as an extension, you must explicitly enable
    1.39 +before you can use it.  (You don't need to download anything; MQ ships
    1.40 +with the standard Mercurial distribution.)  To enable MQ, edit your
    1.41 +\tildefile{.hgrc} file, and add the following lines:
    1.42  
    1.43 -\begin{verbatim}
    1.44 -[extensions]
    1.45 -hgext.mq =
    1.46 -\end{verbatim}
    1.47 +\begin{codesample}
    1.48 +  [extensions]
    1.49 +  hgext.mq =
    1.50 +\end{codesample}
    1.51 +
    1.52 +Once the extension is enabled, it will make a number of new commands
    1.53 +available.  
    1.54 +
    1.55  
    1.56  %%% Local Variables: 
    1.57  %%% mode: latex