hgbook
view en/ch11-mq.xml @ 658:433040113eaf
Update file location in po files
| author | Dongsheng Song <songdongsheng@live.cn> |
|---|---|
| date | Mon Mar 30 21:37:52 2009 +0800 (2009-03-30) |
| parents | 7e7c47481e4f 0b45854f0b7b |
| children | b338f5490029 |
line source
1 <!-- vim: set filetype=docbkxml shiftwidth=2 autoindent expandtab tw=77 : -->
3 <chapter id="chap:mq">
4 <?dbhtml filename="managing-change-with-mercurial-queues.html"?>
5 <title>Managing change with Mercurial Queues</title>
7 <sect1 id="sec:mq:patch-mgmt">
8 <title>The patch management problem</title>
10 <para id="x_3ac">Here is a common scenario: you need to install a software
11 package from source, but you find a bug that you must fix in the
12 source before you can start using the package. You make your
13 changes, forget about the package for a while, and a few months
14 later you need to upgrade to a newer version of the package. If
15 the newer version of the package still has the bug, you must
16 extract your fix from the older source tree and apply it against
17 the newer version. This is a tedious task, and it's easy to
18 make mistakes.</para>
20 <para id="x_3ad">This is a simple case of the <quote>patch management</quote>
21 problem. You have an <quote>upstream</quote> source tree that
22 you can't change; you need to make some local changes on top of
23 the upstream tree; and you'd like to be able to keep those
24 changes separate, so that you can apply them to newer versions
25 of the upstream source.</para>
27 <para id="x_3ae">The patch management problem arises in many situations.
28 Probably the most visible is that a user of an open source
29 software project will contribute a bug fix or new feature to the
30 project's maintainers in the form of a patch.</para>
32 <para id="x_3af">Distributors of operating systems that include open source
33 software often need to make changes to the packages they
34 distribute so that they will build properly in their
35 environments.</para>
37 <para id="x_3b0">When you have few changes to maintain, it is easy to manage
38 a single patch using the standard <command>diff</command> and
39 <command>patch</command> programs (see <xref
40 linkend="sec:mq:patch"/> for a discussion of these
41 tools). Once the number of changes grows, it starts to make
42 sense to maintain patches as discrete <quote>chunks of
43 work,</quote> so that for example a single patch will contain
44 only one bug fix (the patch might modify several files, but it's
45 doing <quote>only one thing</quote>), and you may have a number
46 of such patches for different bugs you need fixed and local
47 changes you require. In this situation, if you submit a bug fix
48 patch to the upstream maintainers of a package and they include
49 your fix in a subsequent release, you can simply drop that
50 single patch when you're updating to the newer release.</para>
52 <para id="x_3b1">Maintaining a single patch against an upstream tree is a
53 little tedious and error-prone, but not difficult. However, the
54 complexity of the problem grows rapidly as the number of patches
55 you have to maintain increases. With more than a tiny number of
56 patches in hand, understanding which ones you have applied and
57 maintaining them moves from messy to overwhelming.</para>
59 <para id="x_3b2">Fortunately, Mercurial includes a powerful extension,
60 Mercurial Queues (or simply <quote>MQ</quote>), that massively
61 simplifies the patch management problem.</para>
63 </sect1>
64 <sect1 id="sec:mq:history">
65 <title>The prehistory of Mercurial Queues</title>
67 <para id="x_3b3">During the late 1990s, several Linux kernel developers
68 started to maintain <quote>patch series</quote> that modified
69 the behaviour of the Linux kernel. Some of these series were
70 focused on stability, some on feature coverage, and others were
71 more speculative.</para>
73 <para id="x_3b4">The sizes of these patch series grew rapidly. In 2002,
74 Andrew Morton published some shell scripts he had been using to
75 automate the task of managing his patch queues. Andrew was
76 successfully using these scripts to manage hundreds (sometimes
77 thousands) of patches on top of the Linux kernel.</para>
79 <sect2 id="sec:mq:quilt">
80 <title>A patchwork quilt</title>
82 <para id="x_3b5">In early 2003, Andreas Gruenbacher and Martin Quinson
83 borrowed the approach of Andrew's scripts and published a tool
84 called <quote>patchwork quilt</quote>
85 <citation>web:quilt</citation>, or simply <quote>quilt</quote>
86 (see <citation>gruenbacher:2005</citation> for a paper
87 describing it). Because quilt substantially automated patch
88 management, it rapidly gained a large following among open
89 source software developers.</para>
91 <para id="x_3b6">Quilt manages a <emphasis>stack of patches</emphasis> on
92 top of a directory tree. To begin, you tell quilt to manage a
93 directory tree, and tell it which files you want to manage; it
94 stores away the names and contents of those files. To fix a
95 bug, you create a new patch (using a single command), edit the
96 files you need to fix, then <quote>refresh</quote> the
97 patch.</para>
99 <para id="x_3b7">The refresh step causes quilt to scan the directory tree;
100 it updates the patch with all of the changes you have made.
101 You can create another patch on top of the first, which will
102 track the changes required to modify the tree from <quote>tree
103 with one patch applied</quote> to <quote>tree with two
104 patches applied</quote>.</para>
106 <para id="x_3b8">You can <emphasis>change</emphasis> which patches are
107 applied to the tree. If you <quote>pop</quote> a patch, the
108 changes made by that patch will vanish from the directory
109 tree. Quilt remembers which patches you have popped, though,
110 so you can <quote>push</quote> a popped patch again, and the
111 directory tree will be restored to contain the modifications
112 in the patch. Most importantly, you can run the
113 <quote>refresh</quote> command at any time, and the topmost
114 applied patch will be updated. This means that you can, at
115 any time, change both which patches are applied and what
116 modifications those patches make.</para>
118 <para id="x_3b9">Quilt knows nothing about revision control tools, so it
119 works equally well on top of an unpacked tarball or a
120 Subversion working copy.</para>
122 </sect2>
123 <sect2 id="sec:mq:quilt-mq">
124 <title>From patchwork quilt to Mercurial Queues</title>
126 <para id="x_3ba">In mid-2005, Chris Mason took the features of quilt and
127 wrote an extension that he called Mercurial Queues, which
128 added quilt-like behaviour to Mercurial.</para>
130 <para id="x_3bb">The key difference between quilt and MQ is that quilt
131 knows nothing about revision control systems, while MQ is
132 <emphasis>integrated</emphasis> into Mercurial. Each patch
133 that you push is represented as a Mercurial changeset. Pop a
134 patch, and the changeset goes away.</para>
136 <para id="x_3bc">Because quilt does not care about revision control tools,
137 it is still a tremendously useful piece of software to know
138 about for situations where you cannot use Mercurial and
139 MQ.</para>
141 </sect2>
142 </sect1>
143 <sect1>
144 <title>The huge advantage of MQ</title>
146 <para id="x_3bd">I cannot overstate the value that MQ offers through the
147 unification of patches and revision control.</para>
149 <para id="x_3be">A major reason that patches have persisted in the free
150 software and open source world&emdash;in spite of the
151 availability of increasingly capable revision control tools over
152 the years&emdash;is the <emphasis>agility</emphasis> they
153 offer.</para>
155 <para id="x_3bf">Traditional revision control tools make a permanent,
156 irreversible record of everything that you do. While this has
157 great value, it's also somewhat stifling. If you want to
158 perform a wild-eyed experiment, you have to be careful in how
159 you go about it, or you risk leaving unneeded&emdash;or worse,
160 misleading or destabilising&emdash;traces of your missteps and
161 errors in the permanent revision record.</para>
163 <para id="x_3c0">By contrast, MQ's marriage of distributed revision control
164 with patches makes it much easier to isolate your work. Your
165 patches live on top of normal revision history, and you can make
166 them disappear or reappear at will. If you don't like a patch,
167 you can drop it. If a patch isn't quite as you want it to be,
168 simply fix it&emdash;as many times as you need to, until you
169 have refined it into the form you desire.</para>
171 <para id="x_3c1">As an example, the integration of patches with revision
172 control makes understanding patches and debugging their
173 effects&emdash;and their interplay with the code they're based
174 on&emdash;<emphasis>enormously</emphasis> easier. Since every
175 applied patch has an associated changeset, you can give <command
176 role="hg-cmd">hg log</command> a file name to see which
177 changesets and patches affected the file. You can use the
178 <command role="hg-cmd">hg bisect</command> command to
179 binary-search through all changesets and applied patches to see
180 where a bug got introduced or fixed. You can use the <command
181 role="hg-cmd">hg annotate</command> command to see which
182 changeset or patch modified a particular line of a source file.
183 And so on.</para>
185 </sect1>
186 <sect1 id="sec:mq:patch">
187 <title>Understanding patches</title>
189 <para id="x_3c2">Because MQ doesn't hide its patch-oriented nature, it is
190 helpful to understand what patches are, and a little about the
191 tools that work with them.</para>
193 <para id="x_3c3">The traditional Unix <command>diff</command> command
194 compares two files, and prints a list of differences between
195 them. The <command>patch</command> command understands these
196 differences as <emphasis>modifications</emphasis> to make to a
197 file. Take a look below for a simple example of these commands
198 in action.</para>
200 &interaction.mq.dodiff.diff;
202 <para id="x_3c4">The type of file that <command>diff</command> generates (and
203 <command>patch</command> takes as input) is called a
204 <quote>patch</quote> or a <quote>diff</quote>; there is no
205 difference between a patch and a diff. (We'll use the term
206 <quote>patch</quote>, since it's more commonly used.)</para>
208 <para id="x_3c5">A patch file can start with arbitrary text; the
209 <command>patch</command> command ignores this text, but MQ uses
210 it as the commit message when creating changesets. To find the
211 beginning of the patch content, <command>patch</command>
212 searches for the first line that starts with the string
213 <quote><literal>diff -</literal></quote>.</para>
215 <para id="x_3c6">MQ works with <emphasis>unified</emphasis> diffs
216 (<command>patch</command> can accept several other diff formats,
217 but MQ doesn't). A unified diff contains two kinds of header.
218 The <emphasis>file header</emphasis> describes the file being
219 modified; it contains the name of the file to modify. When
220 <command>patch</command> sees a new file header, it looks for a
221 file with that name to start modifying.</para>
223 <para id="x_3c7">After the file header comes a series of
224 <emphasis>hunks</emphasis>. Each hunk starts with a header;
225 this identifies the range of line numbers within the file that
226 the hunk should modify. Following the header, a hunk starts and
227 ends with a few (usually three) lines of text from the
228 unmodified file; these are called the
229 <emphasis>context</emphasis> for the hunk. If there's only a
230 small amount of context between successive hunks,
231 <command>diff</command> doesn't print a new hunk header; it just
232 runs the hunks together, with a few lines of context between
233 modifications.</para>
235 <para id="x_3c8">Each line of context begins with a space character. Within
236 the hunk, a line that begins with
237 <quote><literal>-</literal></quote> means <quote>remove this
238 line,</quote> while a line that begins with
239 <quote><literal>+</literal></quote> means <quote>insert this
240 line.</quote> For example, a line that is modified is
241 represented by one deletion and one insertion.</para>
243 <para id="x_3c9">We will return to some of the more subtle aspects of patches
244 later (in <xref linkend="sec:mq:adv-patch"/>), but you
245 should have
246 enough information now to use MQ.</para>
248 </sect1>
249 <sect1 id="sec:mq:start">
250 <title>Getting started with Mercurial Queues</title>
252 <para id="x_3ca">Because MQ is implemented as an extension, you must
253 explicitly enable before you can use it. (You don't need to
254 download anything; MQ ships with the standard Mercurial
255 distribution.) To enable MQ, edit your <filename
256 role="home">~/.hgrc</filename> file, and add the lines
257 below.</para>
259 <programlisting>[extensions]
260 hgext.mq =</programlisting>
262 <para id="x_3cb">Once the extension is enabled, it will make a number of new
263 commands available. To verify that the extension is working,
264 you can use <command role="hg-cmd">hg help</command> to see if
265 the <command role="hg-ext-mq">qinit</command> command is now
266 available.</para>
268 &interaction.mq.qinit-help.help;
270 <para id="x_3cc">You can use MQ with <emphasis>any</emphasis> Mercurial
271 repository, and its commands only operate within that
272 repository. To get started, simply prepare the repository using
273 the <command role="hg-ext-mq">qinit</command> command.</para>
275 &interaction.mq.tutorial.qinit;
277 <para id="x_3cd">This command creates an empty directory called <filename
278 role="special" class="directory">.hg/patches</filename>, where
279 MQ will keep its metadata. As with many Mercurial commands, the
280 <command role="hg-ext-mq">qinit</command> command prints nothing
281 if it succeeds.</para>
283 <sect2>
284 <title>Creating a new patch</title>
286 <para id="x_3ce">To begin work on a new patch, use the <command
287 role="hg-ext-mq">qnew</command> command. This command takes
288 one argument, the name of the patch to create.</para>
290 <para id="x_3cf">MQ will use this as the name of an actual file in the
291 <filename role="special"
292 class="directory">.hg/patches</filename> directory, as you
293 can see below.</para>
295 &interaction.mq.tutorial.qnew;
297 <para id="x_3d0">Also newly present in the <filename role="special"
298 class="directory">.hg/patches</filename> directory are two
299 other files, <filename role="special">series</filename> and
300 <filename role="special">status</filename>. The <filename
301 role="special">series</filename> file lists all of the
302 patches that MQ knows about for this repository, with one
303 patch per line. Mercurial uses the <filename
304 role="special">status</filename> file for internal
305 book-keeping; it tracks all of the patches that MQ has
306 <emphasis>applied</emphasis> in this repository.</para>
308 <note>
309 <para id="x_3d1"> You may sometimes want to edit the <filename
310 role="special">series</filename> file by hand; for
311 example, to change the sequence in which some patches are
312 applied. However, manually editing the <filename
313 role="special">status</filename> file is almost always a
314 bad idea, as it's easy to corrupt MQ's idea of what is
315 happening.</para>
316 </note>
318 <para id="x_3d2">Once you have created your new patch, you can edit files
319 in the working directory as you usually would. All of the
320 normal Mercurial commands, such as <command role="hg-cmd">hg
321 diff</command> and <command role="hg-cmd">hg
322 annotate</command>, work exactly as they did before.</para>
324 </sect2>
325 <sect2>
326 <title>Refreshing a patch</title>
328 <para id="x_3d3">When you reach a point where you want to save your work,
329 use the <command role="hg-ext-mq">qrefresh</command> command
330 to update the patch you are working on.</para>
332 &interaction.mq.tutorial.qrefresh;
334 <para id="x_3d4">This command folds the changes you have made in the
335 working directory into your patch, and updates its
336 corresponding changeset to contain those changes.</para>
338 <para id="x_3d5">You can run <command role="hg-ext-mq">qrefresh</command>
339 as often as you like, so it's a good way to
340 <quote>checkpoint</quote> your work. Refresh your patch at an
341 opportune time; try an experiment; and if the experiment
342 doesn't work out, <command role="hg-cmd">hg revert</command>
343 your modifications back to the last time you refreshed.</para>
345 &interaction.mq.tutorial.qrefresh2;
347 </sect2>
348 <sect2>
349 <title>Stacking and tracking patches</title>
351 <para id="x_3d6">Once you have finished working on a patch, or need to work
352 on another, you can use the <command
353 role="hg-ext-mq">qnew</command> command again to create a
354 new patch. Mercurial will apply this patch on top of your
355 existing patch.</para>
357 &interaction.mq.tutorial.qnew2;
358 <para id="x_3d7">Notice that the patch contains the changes in our prior
359 patch as part of its context (you can see this more clearly in
360 the output of <command role="hg-cmd">hg
361 annotate</command>).</para>
363 <para id="x_3d8">So far, with the exception of <command
364 role="hg-ext-mq">qnew</command> and <command
365 role="hg-ext-mq">qrefresh</command>, we've been careful to
366 only use regular Mercurial commands. However, MQ provides
367 many commands that are easier to use when you are thinking
368 about patches, as illustrated below.</para>
370 &interaction.mq.tutorial.qseries;
372 <itemizedlist>
373 <listitem><para id="x_3d9">The <command
374 role="hg-ext-mq">qseries</command> command lists every
375 patch that MQ knows about in this repository, from oldest
376 to newest (most recently
377 <emphasis>created</emphasis>).</para>
378 </listitem>
379 <listitem><para id="x_3da">The <command
380 role="hg-ext-mq">qapplied</command> command lists every
381 patch that MQ has <emphasis>applied</emphasis> in this
382 repository, again from oldest to newest (most recently
383 applied).</para>
384 </listitem></itemizedlist>
386 </sect2>
387 <sect2>
388 <title>Manipulating the patch stack</title>
390 <para id="x_3db">The previous discussion implied that there must be a
391 difference between <quote>known</quote> and
392 <quote>applied</quote> patches, and there is. MQ can manage a
393 patch without it being applied in the repository.</para>
395 <para id="x_3dc">An <emphasis>applied</emphasis> patch has a corresponding
396 changeset in the repository, and the effects of the patch and
397 changeset are visible in the working directory. You can undo
398 the application of a patch using the <command
399 role="hg-ext-mq">qpop</command> command. MQ still
400 <emphasis>knows about</emphasis>, or manages, a popped patch,
401 but the patch no longer has a corresponding changeset in the
402 repository, and the working directory does not contain the
403 changes made by the patch. <xref
404 linkend="fig:mq:stack"/> illustrates
405 the difference between applied and tracked patches.</para>
407 <figure id="fig:mq:stack">
408 <title>Applied and unapplied patches in the MQ patch
409 stack</title>
410 <mediaobject>
411 <imageobject><imagedata fileref="figs/mq-stack.png"/></imageobject>
412 <textobject><phrase>XXX add text</phrase></textobject>
413 </mediaobject>
414 </figure>
416 <para id="x_3de">You can reapply an unapplied, or popped, patch using the
417 <command role="hg-ext-mq">qpush</command> command. This
418 creates a new changeset to correspond to the patch, and the
419 patch's changes once again become present in the working
420 directory. See below for examples of <command
421 role="hg-ext-mq">qpop</command> and <command
422 role="hg-ext-mq">qpush</command> in action.</para>
423 &interaction.mq.tutorial.qpop;
425 <para id="x_3df">Notice that once we have popped a patch or two patches,
426 the output of <command role="hg-ext-mq">qseries</command>
427 remains the same, while that of <command
428 role="hg-ext-mq">qapplied</command> has changed.</para>
431 </sect2>
432 <sect2>
433 <title>Pushing and popping many patches</title>
435 <para id="x_3e0">While <command role="hg-ext-mq">qpush</command> and
436 <command role="hg-ext-mq">qpop</command> each operate on a
437 single patch at a time by default, you can push and pop many
438 patches in one go. The <option
439 role="hg-ext-mq-cmd-qpush-opt">hg -a</option> option to
440 <command role="hg-ext-mq">qpush</command> causes it to push
441 all unapplied patches, while the <option
442 role="hg-ext-mq-cmd-qpop-opt">-a</option> option to <command
443 role="hg-ext-mq">qpop</command> causes it to pop all applied
444 patches. (For some more ways to push and pop many patches,
445 see <xref linkend="sec:mq:perf"/> below.)</para>
447 &interaction.mq.tutorial.qpush-a;
449 </sect2>
450 <sect2>
451 <title>Safety checks, and overriding them</title>
453 <para id="x_3e1">Several MQ commands check the working directory before
454 they do anything, and fail if they find any modifications.
455 They do this to ensure that you won't lose any changes that
456 you have made, but not yet incorporated into a patch. The
457 example below illustrates this; the <command
458 role="hg-ext-mq">qnew</command> command will not create a
459 new patch if there are outstanding changes, caused in this
460 case by the <command role="hg-cmd">hg add</command> of
461 <filename>file3</filename>.</para>
463 &interaction.mq.tutorial.add;
465 <para id="x_3e2">Commands that check the working directory all take an
466 <quote>I know what I'm doing</quote> option, which is always
467 named <option>-f</option>. The exact meaning of
468 <option>-f</option> depends on the command. For example,
469 <command role="hg-cmd">hg qnew <option
470 role="hg-ext-mq-cmd-qnew-opt">hg -f</option></command>
471 will incorporate any outstanding changes into the new patch it
472 creates, but <command role="hg-cmd">hg qpop <option
473 role="hg-ext-mq-cmd-qpop-opt">hg -f</option></command>
474 will revert modifications to any files affected by the patch
475 that it is popping. Be sure to read the documentation for a
476 command's <option>-f</option> option before you use it!</para>
478 </sect2>
479 <sect2>
480 <title>Working on several patches at once</title>
482 <para id="x_3e3">The <command role="hg-ext-mq">qrefresh</command> command
483 always refreshes the <emphasis>topmost</emphasis> applied
484 patch. This means that you can suspend work on one patch (by
485 refreshing it), pop or push to make a different patch the top,
486 and work on <emphasis>that</emphasis> patch for a
487 while.</para>
489 <para id="x_3e4">Here's an example that illustrates how you can use this
490 ability. Let's say you're developing a new feature as two
491 patches. The first is a change to the core of your software,
492 and the second&emdash;layered on top of the
493 first&emdash;changes the user interface to use the code you
494 just added to the core. If you notice a bug in the core while
495 you're working on the UI patch, it's easy to fix the core.
496 Simply <command role="hg-ext-mq">qrefresh</command> the UI
497 patch to save your in-progress changes, and <command
498 role="hg-ext-mq">qpop</command> down to the core patch. Fix
499 the core bug, <command role="hg-ext-mq">qrefresh</command> the
500 core patch, and <command role="hg-ext-mq">qpush</command> back
501 to the UI patch to continue where you left off.</para>
503 </sect2>
504 </sect1>
505 <sect1 id="sec:mq:adv-patch">
506 <title>More about patches</title>
508 <para id="x_3e5">MQ uses the GNU <command>patch</command> command to apply
509 patches, so it's helpful to know a few more detailed aspects of
510 how <command>patch</command> works, and about patches
511 themselves.</para>
513 <sect2>
514 <title>The strip count</title>
516 <para id="x_3e6">If you look at the file headers in a patch, you will
517 notice that the pathnames usually have an extra component on
518 the front that isn't present in the actual path name. This is
519 a holdover from the way that people used to generate patches
520 (people still do this, but it's somewhat rare with modern
521 revision control tools).</para>
523 <para id="x_3e7">Alice would unpack a tarball, edit her files, then decide
524 that she wanted to create a patch. So she'd rename her
525 working directory, unpack the tarball again (hence the need
526 for the rename), and use the <option
527 role="cmd-opt-diff">-r</option> and <option
528 role="cmd-opt-diff">-N</option> options to
529 <command>diff</command> to recursively generate a patch
530 between the unmodified directory and the modified one. The
531 result would be that the name of the unmodified directory
532 would be at the front of the left-hand path in every file
533 header, and the name of the modified directory would be at the
534 front of the right-hand path.</para>
536 <para id="x_3e8">Since someone receiving a patch from the Alices of the net
537 would be unlikely to have unmodified and modified directories
538 with exactly the same names, the <command>patch</command>
539 command has a <option role="cmd-opt-patch">-p</option> option
540 that indicates the number of leading path name components to
541 strip when trying to apply a patch. This number is called the
542 <emphasis>strip count</emphasis>.</para>
544 <para id="x_3e9">An option of <quote><literal>-p1</literal></quote> means
545 <quote>use a strip count of one</quote>. If
546 <command>patch</command> sees a file name
547 <filename>foo/bar/baz</filename> in a file header, it will
548 strip <filename>foo</filename> and try to patch a file named
549 <filename>bar/baz</filename>. (Strictly speaking, the strip
550 count refers to the number of <emphasis>path
551 separators</emphasis> (and the components that go with them
552 ) to strip. A strip count of one will turn
553 <filename>foo/bar</filename> into <filename>bar</filename>,
554 but <filename>/foo/bar</filename> (notice the extra leading
555 slash) into <filename>foo/bar</filename>.)</para>
557 <para id="x_3ea">The <quote>standard</quote> strip count for patches is
558 one; almost all patches contain one leading path name
559 component that needs to be stripped. Mercurial's <command
560 role="hg-cmd">hg diff</command> command generates path names
561 in this form, and the <command role="hg-cmd">hg
562 import</command> command and MQ expect patches to have a
563 strip count of one.</para>
565 <para id="x_3eb">If you receive a patch from someone that you want to add
566 to your patch queue, and the patch needs a strip count other
567 than one, you cannot just <command
568 role="hg-ext-mq">qimport</command> the patch, because
569 <command role="hg-ext-mq">qimport</command> does not yet have
570 a <literal>-p</literal> option (see <ulink role="hg-bug"
571 url="http://www.selenic.com/mercurial/bts/issue311">issue
572 311</ulink>). Your best bet is to <command
573 role="hg-ext-mq">qnew</command> a patch of your own, then
574 use <command>patch -pN</command> to apply their patch,
575 followed by <command role="hg-cmd">hg addremove</command> to
576 pick up any files added or removed by the patch, followed by
577 <command role="hg-ext-mq">hg qrefresh</command>. This
578 complexity may become unnecessary; see <ulink role="hg-bug"
579 url="http://www.selenic.com/mercurial/bts/issue311">issue
580 311</ulink> for details.
581 </para>
582 </sect2>
583 <sect2>
584 <title>Strategies for applying a patch</title>
586 <para id="x_3ec">When <command>patch</command> applies a hunk, it tries a
587 handful of successively less accurate strategies to try to
588 make the hunk apply. This falling-back technique often makes
589 it possible to take a patch that was generated against an old
590 version of a file, and apply it against a newer version of
591 that file.</para>
593 <para id="x_3ed">First, <command>patch</command> tries an exact match,
594 where the line numbers, the context, and the text to be
595 modified must apply exactly. If it cannot make an exact
596 match, it tries to find an exact match for the context,
597 without honouring the line numbering information. If this
598 succeeds, it prints a line of output saying that the hunk was
599 applied, but at some <emphasis>offset</emphasis> from the
600 original line number.</para>
602 <para id="x_3ee">If a context-only match fails, <command>patch</command>
603 removes the first and last lines of the context, and tries a
604 <emphasis>reduced</emphasis> context-only match. If the hunk
605 with reduced context succeeds, it prints a message saying that
606 it applied the hunk with a <emphasis>fuzz factor</emphasis>
607 (the number after the fuzz factor indicates how many lines of
608 context <command>patch</command> had to trim before the patch
609 applied).</para>
611 <para id="x_3ef">When neither of these techniques works,
612 <command>patch</command> prints a message saying that the hunk
613 in question was rejected. It saves rejected hunks (also
614 simply called <quote>rejects</quote>) to a file with the same
615 name, and an added <filename role="special">.rej</filename>
616 extension. It also saves an unmodified copy of the file with
617 a <filename role="special">.orig</filename> extension; the
618 copy of the file without any extensions will contain any
619 changes made by hunks that <emphasis>did</emphasis> apply
620 cleanly. If you have a patch that modifies
621 <filename>foo</filename> with six hunks, and one of them fails
622 to apply, you will have: an unmodified
623 <filename>foo.orig</filename>, a <filename>foo.rej</filename>
624 containing one hunk, and <filename>foo</filename>, containing
625 the changes made by the five successful hunks.</para>
627 </sect2>
628 <sect2>
629 <title>Some quirks of patch representation</title>
631 <para id="x_3f0">There are a few useful things to know about how
632 <command>patch</command> works with files.</para>
633 <itemizedlist>
634 <listitem><para id="x_3f1">This should already be obvious, but
635 <command>patch</command> cannot handle binary
636 files.</para>
637 </listitem>
638 <listitem><para id="x_3f2">Neither does it care about the executable bit;
639 it creates new files as readable, but not
640 executable.</para>
641 </listitem>
642 <listitem><para id="x_3f3"><command>patch</command> treats the removal of
643 a file as a diff between the file to be removed and the
644 empty file. So your idea of <quote>I deleted this
645 file</quote> looks like <quote>every line of this file
646 was deleted</quote> in a patch.</para>
647 </listitem>
648 <listitem><para id="x_3f4">It treats the addition of a file as a diff
649 between the empty file and the file to be added. So in a
650 patch, your idea of <quote>I added this file</quote> looks
651 like <quote>every line of this file was
652 added</quote>.</para>
653 </listitem>
654 <listitem><para id="x_3f5">It treats a renamed file as the removal of the
655 old name, and the addition of the new name. This means
656 that renamed files have a big footprint in patches. (Note
657 also that Mercurial does not currently try to infer when
658 files have been renamed or copied in a patch.)</para>
659 </listitem>
660 <listitem><para id="x_3f6"><command>patch</command> cannot represent
661 empty files, so you cannot use a patch to represent the
662 notion <quote>I added this empty file to the
663 tree</quote>.</para>
664 </listitem></itemizedlist>
665 </sect2>
666 <sect2>
667 <title>Beware the fuzz</title>
669 <para id="x_3f7">While applying a hunk at an offset, or with a fuzz factor,
670 will often be completely successful, these inexact techniques
671 naturally leave open the possibility of corrupting the patched
672 file. The most common cases typically involve applying a
673 patch twice, or at an incorrect location in the file. If
674 <command>patch</command> or <command
675 role="hg-ext-mq">qpush</command> ever mentions an offset or
676 fuzz factor, you should make sure that the modified files are
677 correct afterwards.</para>
679 <para id="x_3f8">It's often a good idea to refresh a patch that has applied
680 with an offset or fuzz factor; refreshing the patch generates
681 new context information that will make it apply cleanly. I
682 say <quote>often,</quote> not <quote>always,</quote> because
683 sometimes refreshing a patch will make it fail to apply
684 against a different revision of the underlying files. In some
685 cases, such as when you're maintaining a patch that must sit
686 on top of multiple versions of a source tree, it's acceptable
687 to have a patch apply with some fuzz, provided you've verified
688 the results of the patching process in such cases.</para>
690 </sect2>
691 <sect2>
692 <title>Handling rejection</title>
694 <para id="x_3f9">If <command role="hg-ext-mq">qpush</command> fails to
695 apply a patch, it will print an error message and exit. If it
696 has left <filename role="special">.rej</filename> files
697 behind, it is usually best to fix up the rejected hunks before
698 you push more patches or do any further work.</para>
700 <para id="x_3fa">If your patch <emphasis>used to</emphasis> apply cleanly,
701 and no longer does because you've changed the underlying code
702 that your patches are based on, Mercurial Queues can help; see
703 <xref linkend="sec:mq:merge"/> for details.</para>
705 <para id="x_3fb">Unfortunately, there aren't any great techniques for
706 dealing with rejected hunks. Most often, you'll need to view
707 the <filename role="special">.rej</filename> file and edit the
708 target file, applying the rejected hunks by hand.</para>
710 <para id="x_3fc">If you're feeling adventurous, Neil Brown, a Linux kernel
711 hacker, wrote a tool called <command>wiggle</command>
712 <citation>web:wiggle</citation>, which is more vigorous than
713 <command>patch</command> in its attempts to make a patch
714 apply.</para>
716 <para id="x_3fd">Another Linux kernel hacker, Chris Mason (the author of
717 Mercurial Queues), wrote a similar tool called
718 <command>mpatch</command> <citation>web:mpatch</citation>,
719 which takes a simple approach to automating the application of
720 hunks rejected by <command>patch</command>. The
721 <command>mpatch</command> command can help with four common
722 reasons that a hunk may be rejected:</para>
724 <itemizedlist>
725 <listitem><para id="x_3fe">The context in the middle of a hunk has
726 changed.</para>
727 </listitem>
728 <listitem><para id="x_3ff">A hunk is missing some context at the
729 beginning or end.</para>
730 </listitem>
731 <listitem><para id="x_400">A large hunk might apply better&emdash;either
732 entirely or in part&emdash;if it was broken up into
733 smaller hunks.</para>
734 </listitem>
735 <listitem><para id="x_401">A hunk removes lines with slightly different
736 content than those currently present in the file.</para>
737 </listitem></itemizedlist>
739 <para id="x_402">If you use <command>wiggle</command> or
740 <command>mpatch</command>, you should be doubly careful to
741 check your results when you're done. In fact,
742 <command>mpatch</command> enforces this method of
743 double-checking the tool's output, by automatically dropping
744 you into a merge program when it has done its job, so that you
745 can verify its work and finish off any remaining
746 merges.</para>
748 </sect2>
749 </sect1>
750 <sect1 id="sec:mq:perf">
751 <title>Getting the best performance out of MQ</title>
753 <para id="x_403">MQ is very efficient at handling a large number of patches.
754 I ran some performance experiments in mid-2006 for a talk that I
755 gave at the 2006 EuroPython conference
756 <citation>web:europython</citation>. I used as my data set the
757 Linux 2.6.17-mm1 patch series, which consists of 1,738 patches.
758 I applied these on top of a Linux kernel repository containing
759 all 27,472 revisions between Linux 2.6.12-rc2 and Linux
760 2.6.17.</para>
762 <para id="x_404">On my old, slow laptop, I was able to <command
763 role="hg-cmd">hg qpush <option
764 role="hg-ext-mq-cmd-qpush-opt">hg -a</option></command> all
765 1,738 patches in 3.5 minutes, and <command role="hg-cmd">hg qpop
766 <option role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command>
767 them all in 30 seconds. (On a newer laptop, the time to push
768 all patches dropped to two minutes.) I could <command
769 role="hg-ext-mq">qrefresh</command> one of the biggest patches
770 (which made 22,779 lines of changes to 287 files) in 6.6
771 seconds.</para>
773 <para id="x_405">Clearly, MQ is well suited to working in large trees, but
774 there are a few tricks you can use to get the best performance
775 of it.</para>
777 <para id="x_406">First of all, try to <quote>batch</quote> operations
778 together. Every time you run <command
779 role="hg-ext-mq">qpush</command> or <command
780 role="hg-ext-mq">qpop</command>, these commands scan the
781 working directory once to make sure you haven't made some
782 changes and then forgotten to run <command
783 role="hg-ext-mq">qrefresh</command>. On a small tree, the
784 time that this scan takes is unnoticeable. However, on a
785 medium-sized tree (containing tens of thousands of files), it
786 can take a second or more.</para>
788 <para id="x_407">The <command role="hg-ext-mq">qpush</command> and <command
789 role="hg-ext-mq">qpop</command> commands allow you to push and
790 pop multiple patches at a time. You can identify the
791 <quote>destination patch</quote> that you want to end up at.
792 When you <command role="hg-ext-mq">qpush</command> with a
793 destination specified, it will push patches until that patch is
794 at the top of the applied stack. When you <command
795 role="hg-ext-mq">qpop</command> to a destination, MQ will pop
796 patches until the destination patch is at the top.</para>
798 <para id="x_408">You can identify a destination patch using either the name
799 of the patch, or by number. If you use numeric addressing,
800 patches are counted from zero; this means that the first patch
801 is zero, the second is one, and so on.</para>
803 </sect1>
804 <sect1 id="sec:mq:merge">
805 <title>Updating your patches when the underlying code
806 changes</title>
808 <para id="x_409">It's common to have a stack of patches on top of an
809 underlying repository that you don't modify directly. If you're
810 working on changes to third-party code, or on a feature that is
811 taking longer to develop than the rate of change of the code
812 beneath, you will often need to sync up with the underlying
813 code, and fix up any hunks in your patches that no longer apply.
814 This is called <emphasis>rebasing</emphasis> your patch
815 series.</para>
817 <para id="x_40a">The simplest way to do this is to <command role="hg-cmd">hg
818 qpop <option role="hg-ext-mq-cmd-qpop-opt">hg
819 -a</option></command> your patches, then <command
820 role="hg-cmd">hg pull</command> changes into the underlying
821 repository, and finally <command role="hg-cmd">hg qpush <option
822 role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command> your
823 patches again. MQ will stop pushing any time it runs across a
824 patch that fails to apply during conflicts, allowing you to fix
825 your conflicts, <command role="hg-ext-mq">qrefresh</command> the
826 affected patch, and continue pushing until you have fixed your
827 entire stack.</para>
829 <para id="x_40b">This approach is easy to use and works well if you don't
830 expect changes to the underlying code to affect how well your
831 patches apply. If your patch stack touches code that is modified
832 frequently or invasively in the underlying repository, however,
833 fixing up rejected hunks by hand quickly becomes
834 tiresome.</para>
836 <para id="x_40c">It's possible to partially automate the rebasing process.
837 If your patches apply cleanly against some revision of the
838 underlying repo, MQ can use this information to help you to
839 resolve conflicts between your patches and a different
840 revision.</para>
842 <para id="x_40d">The process is a little involved.</para>
843 <orderedlist>
844 <listitem><para id="x_40e">To begin, <command role="hg-cmd">hg qpush
845 -a</command> all of your patches on top of the revision
846 where you know that they apply cleanly.</para>
847 </listitem>
848 <listitem><para id="x_40f">Save a backup copy of your patch directory using
849 <command role="hg-cmd">hg qsave <option
850 role="hg-ext-mq-cmd-qsave-opt">hg -e</option> <option
851 role="hg-ext-mq-cmd-qsave-opt">hg -c</option></command>.
852 This prints the name of the directory that it has saved the
853 patches in. It will save the patches to a directory called
854 <filename role="special"
855 class="directory">.hg/patches.N</filename>, where
856 <literal>N</literal> is a small integer. It also commits a
857 <quote>save changeset</quote> on top of your applied
858 patches; this is for internal book-keeping, and records the
859 states of the <filename role="special">series</filename> and
860 <filename role="special">status</filename> files.</para>
861 </listitem>
862 <listitem><para id="x_410">Use <command role="hg-cmd">hg pull</command> to
863 bring new changes into the underlying repository. (Don't
864 run <command role="hg-cmd">hg pull -u</command>; see below
865 for why.)</para>
866 </listitem>
867 <listitem><para id="x_411">Update to the new tip revision, using <command
868 role="hg-cmd">hg update <option
869 role="hg-opt-update">-C</option></command> to override
870 the patches you have pushed.</para>
871 </listitem>
872 <listitem><para id="x_412">Merge all patches using <command>hg qpush -m
873 -a</command>. The <option
874 role="hg-ext-mq-cmd-qpush-opt">-m</option> option to
875 <command role="hg-ext-mq">qpush</command> tells MQ to
876 perform a three-way merge if the patch fails to
877 apply.</para>
878 </listitem></orderedlist>
880 <para id="x_413">During the <command role="hg-cmd">hg qpush <option
881 role="hg-ext-mq-cmd-qpush-opt">hg -m</option></command>,
882 each patch in the <filename role="special">series</filename>
883 file is applied normally. If a patch applies with fuzz or
884 rejects, MQ looks at the queue you <command
885 role="hg-ext-mq">qsave</command>d, and performs a three-way
886 merge with the corresponding changeset. This merge uses
887 Mercurial's normal merge machinery, so it may pop up a GUI merge
888 tool to help you to resolve problems.</para>
890 <para id="x_414">When you finish resolving the effects of a patch, MQ
891 refreshes your patch based on the result of the merge.</para>
893 <para id="x_415">At the end of this process, your repository will have one
894 extra head from the old patch queue, and a copy of the old patch
895 queue will be in <filename role="special"
896 class="directory">.hg/patches.N</filename>. You can remove the
897 extra head using <command role="hg-cmd">hg qpop -a -n
898 patches.N</command> or <command role="hg-cmd">hg
899 strip</command>. You can delete <filename role="special"
900 class="directory">.hg/patches.N</filename> once you are sure
901 that you no longer need it as a backup.</para>
903 </sect1>
904 <sect1>
905 <title>Identifying patches</title>
907 <para id="x_416">MQ commands that work with patches let you refer to a patch
908 either by using its name or by a number. By name is obvious
909 enough; pass the name <filename>foo.patch</filename> to <command
910 role="hg-ext-mq">qpush</command>, for example, and it will
911 push patches until <filename>foo.patch</filename> is
912 applied.</para>
914 <para id="x_417">As a shortcut, you can refer to a patch using both a name
915 and a numeric offset; <literal>foo.patch-2</literal> means
916 <quote>two patches before <literal>foo.patch</literal></quote>,
917 while <literal>bar.patch+4</literal> means <quote>four patches
918 after <literal>bar.patch</literal></quote>.</para>
920 <para id="x_418">Referring to a patch by index isn't much different. The
921 first patch printed in the output of <command
922 role="hg-ext-mq">qseries</command> is patch zero (yes, it's
923 one of those start-at-zero counting systems); the second is
924 patch one; and so on.</para>
926 <para id="x_419">MQ also makes it easy to work with patches when you are
927 using normal Mercurial commands. Every command that accepts a
928 changeset ID will also accept the name of an applied patch. MQ
929 augments the tags normally in the repository with an eponymous
930 one for each applied patch. In addition, the special tags
931 <literal role="tag">qbase</literal> and
932 <literal role="tag">qtip</literal> identify
933 the <quote>bottom-most</quote> and topmost applied patches,
934 respectively.</para>
936 <para id="x_41a">These additions to Mercurial's normal tagging capabilities
937 make dealing with patches even more of a breeze.</para>
938 <itemizedlist>
939 <listitem><para id="x_41b">Want to patchbomb a mailing list with your
940 latest series of changes?</para>
941 <programlisting>hg email qbase:qtip</programlisting>
942 <para id="x_41c"> (Don't know what <quote>patchbombing</quote> is? See
943 <xref linkend="sec:hgext:patchbomb"/>.)</para>
944 </listitem>
945 <listitem><para id="x_41d">Need to see all of the patches since
946 <literal>foo.patch</literal> that have touched files in a
947 subdirectory of your tree?</para>
948 <programlisting>hg log -r foo.patch:qtip subdir</programlisting>
949 </listitem>
950 </itemizedlist>
952 <para id="x_41e">Because MQ makes the names of patches available to the rest
953 of Mercurial through its normal internal tag machinery, you
954 don't need to type in the entire name of a patch when you want
955 to identify it by name.</para>
957 <para id="x_41f">Another nice consequence of representing patch names as tags
958 is that when you run the <command role="hg-cmd">hg log</command>
959 command, it will display a patch's name as a tag, simply as part
960 of its normal output. This makes it easy to visually
961 distinguish applied patches from underlying
962 <quote>normal</quote> revisions. The following example shows a
963 few normal Mercurial commands in use with applied
964 patches.</para>
966 &interaction.mq.id.output;
968 </sect1>
969 <sect1>
970 <title>Useful things to know about</title>
972 <para id="x_420">There are a number of aspects of MQ usage that don't fit
973 tidily into sections of their own, but that are good to know.
974 Here they are, in one place.</para>
976 <itemizedlist>
977 <listitem><para id="x_421">Normally, when you <command
978 role="hg-ext-mq">qpop</command> a patch and <command
979 role="hg-ext-mq">qpush</command> it again, the changeset
980 that represents the patch after the pop/push will have a
981 <emphasis>different identity</emphasis> than the changeset
982 that represented the hash beforehand. See <xref
983 linkend="sec:mqref:cmd:qpush"/> for
984 information as to why this is.</para>
985 </listitem>
986 <listitem><para id="x_422">It's not a good idea to <command
987 role="hg-cmd">hg merge</command> changes from another
988 branch with a patch changeset, at least if you want to
989 maintain the <quote>patchiness</quote> of that changeset and
990 changesets below it on the patch stack. If you try to do
991 this, it will appear to succeed, but MQ will become
992 confused.</para>
993 </listitem></itemizedlist>
995 </sect1>
996 <sect1 id="sec:mq:repo">
997 <title>Managing patches in a repository</title>
999 <para id="x_423">Because MQ's <filename role="special"
1000 class="directory">.hg/patches</filename> directory resides
1001 outside a Mercurial repository's working directory, the
1002 <quote>underlying</quote> Mercurial repository knows nothing
1003 about the management or presence of patches.</para>
1005 <para id="x_424">This presents the interesting possibility of managing the
1006 contents of the patch directory as a Mercurial repository in its
1007 own right. This can be a useful way to work. For example, you
1008 can work on a patch for a while, <command
1009 role="hg-ext-mq">qrefresh</command> it, then <command
1010 role="hg-cmd">hg commit</command> the current state of the
1011 patch. This lets you <quote>roll back</quote> to that version
1012 of the patch later on.</para>
1014 <para id="x_425">You can then share different versions of the same patch
1015 stack among multiple underlying repositories. I use this when I
1016 am developing a Linux kernel feature. I have a pristine copy of
1017 my kernel sources for each of several CPU architectures, and a
1018 cloned repository under each that contains the patches I am
1019 working on. When I want to test a change on a different
1020 architecture, I push my current patches to the patch repository
1021 associated with that kernel tree, pop and push all of my
1022 patches, and build and test that kernel.</para>
1024 <para id="x_426">Managing patches in a repository makes it possible for
1025 multiple developers to work on the same patch series without
1026 colliding with each other, all on top of an underlying source
1027 base that they may or may not control.</para>
1029 <sect2>
1030 <title>MQ support for patch repositories</title>
1032 <para id="x_427">MQ helps you to work with the <filename role="special"
1033 class="directory">.hg/patches</filename> directory as a
1034 repository; when you prepare a repository for working with
1035 patches using <command role="hg-ext-mq">qinit</command>, you
1036 can pass the <option role="hg-ext-mq-cmd-qinit-opt">hg
1037 -c</option> option to create the <filename role="special"
1038 class="directory">.hg/patches</filename> directory as a
1039 Mercurial repository.</para>
1041 <note>
1042 <para id="x_428"> If you forget to use the <option
1043 role="hg-ext-mq-cmd-qinit-opt">hg -c</option> option, you
1044 can simply go into the <filename role="special"
1045 class="directory">.hg/patches</filename> directory at any
1046 time and run <command role="hg-cmd">hg init</command>.
1047 Don't forget to add an entry for the <filename
1048 role="special">status</filename> file to the <filename
1049 role="special">.hgignore</filename> file, though</para>
1051 <para id="x_429"> (<command role="hg-cmd">hg qinit <option
1052 role="hg-ext-mq-cmd-qinit-opt">hg -c</option></command>
1053 does this for you automatically); you
1054 <emphasis>really</emphasis> don't want to manage the
1055 <filename role="special">status</filename> file.</para>
1056 </note>
1058 <para id="x_42a">As a convenience, if MQ notices that the <filename
1059 class="directory">.hg/patches</filename> directory is a
1060 repository, it will automatically <command role="hg-cmd">hg
1061 add</command> every patch that you create and import.</para>
1063 <para id="x_42b">MQ provides a shortcut command, <command
1064 role="hg-ext-mq">qcommit</command>, that runs <command
1065 role="hg-cmd">hg commit</command> in the <filename
1066 role="special" class="directory">.hg/patches</filename>
1067 directory. This saves some bothersome typing.</para>
1069 <para id="x_42c">Finally, as a convenience to manage the patch directory,
1070 you can define the alias <command>mq</command> on Unix
1071 systems. For example, on Linux systems using the
1072 <command>bash</command> shell, you can include the following
1073 snippet in your <filename
1074 role="home">~/.bashrc</filename>.</para>
1076 <programlisting>alias mq=`hg -R $(hg root)/.hg/patches'</programlisting>
1078 <para id="x_42d">You can then issue commands of the form <command>mq
1079 pull</command> from the main repository.</para>
1081 </sect2>
1082 <sect2>
1083 <title>A few things to watch out for</title>
1085 <para id="x_42e">MQ's support for working with a repository full of patches
1086 is limited in a few small respects.</para>
1088 <para id="x_42f">MQ cannot automatically detect changes that you make to
1089 the patch directory. If you <command role="hg-cmd">hg
1090 pull</command>, manually edit, or <command role="hg-cmd">hg
1091 update</command> changes to patches or the <filename
1092 role="special">series</filename> file, you will have to
1093 <command role="hg-cmd">hg qpop <option
1094 role="hg-ext-mq-cmd-qpop-opt">hg -a</option></command> and
1095 then <command role="hg-cmd">hg qpush <option
1096 role="hg-ext-mq-cmd-qpush-opt">hg -a</option></command> in
1097 the underlying repository to see those changes show up there.
1098 If you forget to do this, you can confuse MQ's idea of which
1099 patches are applied.</para>
1101 </sect2>
1102 </sect1>
1103 <sect1 id="sec:mq:tools">
1104 <title>Third party tools for working with patches</title>
1106 <para id="x_430">Once you've been working with patches for a while, you'll
1107 find yourself hungry for tools that will help you to understand
1108 and manipulate the patches you're dealing with.</para>
1110 <para id="x_431">The <command>diffstat</command> command
1111 <citation>web:diffstat</citation> generates a histogram of the
1112 modifications made to each file in a patch. It provides a good
1113 way to <quote>get a sense of</quote> a patch&emdash;which files
1114 it affects, and how much change it introduces to each file and
1115 as a whole. (I find that it's a good idea to use
1116 <command>diffstat</command>'s <option
1117 role="cmd-opt-diffstat">-p</option> option as a matter of
1118 course, as otherwise it will try to do clever things with
1119 prefixes of file names that inevitably confuse at least
1120 me.)</para>
1122 &interaction.mq.tools.tools;
1124 <para id="x_432">The <literal role="package">patchutils</literal> package
1125 <citation>web:patchutils</citation> is invaluable. It provides a
1126 set of small utilities that follow the <quote>Unix
1127 philosophy;</quote> each does one useful thing with a patch.
1128 The <literal role="package">patchutils</literal> command I use
1129 most is <command>filterdiff</command>, which extracts subsets
1130 from a patch file. For example, given a patch that modifies
1131 hundreds of files across dozens of directories, a single
1132 invocation of <command>filterdiff</command> can generate a
1133 smaller patch that only touches files whose names match a
1134 particular glob pattern. See <xref
1135 linkend="mq-collab:tips:interdiff"/> for another
1136 example.</para>
1138 </sect1>
1139 <sect1>
1140 <title>Good ways to work with patches</title>
1142 <para id="x_433">Whether you are working on a patch series to submit to a
1143 free software or open source project, or a series that you
1144 intend to treat as a sequence of regular changesets when you're
1145 done, you can use some simple techniques to keep your work well
1146 organised.</para>
1148 <para id="x_434">Give your patches descriptive names. A good name for a
1149 patch might be <filename>rework-device-alloc.patch</filename>,
1150 because it will immediately give you a hint what the purpose of
1151 the patch is. Long names shouldn't be a problem; you won't be
1152 typing the names often, but you <emphasis>will</emphasis> be
1153 running commands like <command
1154 role="hg-ext-mq">qapplied</command> and <command
1155 role="hg-ext-mq">qtop</command> over and over. Good naming
1156 becomes especially important when you have a number of patches
1157 to work with, or if you are juggling a number of different tasks
1158 and your patches only get a fraction of your attention.</para>
1160 <para id="x_435">Be aware of what patch you're working on. Use the <command
1161 role="hg-ext-mq">qtop</command> command and skim over the text
1162 of your patches frequently&emdash;for example, using <command
1163 role="hg-cmd">hg tip <option
1164 role="hg-opt-tip">-p</option></command>)&emdash;to be sure
1165 of where you stand. I have several times worked on and <command
1166 role="hg-ext-mq">qrefresh</command>ed a patch other than the
1167 one I intended, and it's often tricky to migrate changes into
1168 the right patch after making them in the wrong one.</para>
1170 <para id="x_436">For this reason, it is very much worth investing a little
1171 time to learn how to use some of the third-party tools I
1172 described in <xref linkend="sec:mq:tools"/>,
1173 particularly
1174 <command>diffstat</command> and <command>filterdiff</command>.
1175 The former will give you a quick idea of what changes your patch
1176 is making, while the latter makes it easy to splice hunks
1177 selectively out of one patch and into another.</para>
1179 </sect1>
1180 <sect1>
1181 <title>MQ cookbook</title>
1183 <sect2>
1184 <title>Manage <quote>trivial</quote> patches</title>
1186 <para id="x_437">Because the overhead of dropping files into a new
1187 Mercurial repository is so low, it makes a lot of sense to
1188 manage patches this way even if you simply want to make a few
1189 changes to a source tarball that you downloaded.</para>
1191 <para id="x_438">Begin by downloading and unpacking the source tarball, and
1192 turning it into a Mercurial repository.</para>
1194 &interaction.mq.tarball.download;
1196 <para id="x_439">Continue by creating a patch stack and making your
1197 changes.</para>
1199 &interaction.mq.tarball.qinit;
1201 <para id="x_43a">Let's say a few weeks or months pass, and your package
1202 author releases a new version. First, bring their changes
1203 into the repository.</para>
1205 &interaction.mq.tarball.newsource;
1207 <para id="x_43b">The pipeline starting with <command role="hg-cmd">hg
1208 locate</command> above deletes all files in the working
1209 directory, so that <command role="hg-cmd">hg
1210 commit</command>'s <option
1211 role="hg-opt-commit">--addremove</option> option can
1212 actually tell which files have really been removed in the
1213 newer version of the source.</para>
1215 <para id="x_43c">Finally, you can apply your patches on top of the new
1216 tree.</para>
1218 &interaction.mq.tarball.repush;
1220 </sect2>
1221 <sect2 id="sec:mq:combine">
1222 <title>Combining entire patches</title>
1224 <para id="x_43d">MQ provides a command, <command
1225 role="hg-ext-mq">qfold</command> that lets you combine
1226 entire patches. This <quote>folds</quote> the patches you
1227 name, in the order you name them, into the topmost applied
1228 patch, and concatenates their descriptions onto the end of its
1229 description. The patches that you fold must be unapplied
1230 before you fold them.</para>
1232 <para id="x_43e">The order in which you fold patches matters. If your
1233 topmost applied patch is <literal>foo</literal>, and you
1234 <command role="hg-ext-mq">qfold</command>
1235 <literal>bar</literal> and <literal>quux</literal> into it,
1236 you will end up with a patch that has the same effect as if
1237 you applied first <literal>foo</literal>, then
1238 <literal>bar</literal>, followed by
1239 <literal>quux</literal>.</para>
1241 </sect2>
1242 <sect2>
1243 <title>Merging part of one patch into another</title>
1245 <para id="x_43f">Merging <emphasis>part</emphasis> of one patch into
1246 another is more difficult than combining entire
1247 patches.</para>
1249 <para id="x_440">If you want to move changes to entire files, you can use
1250 <command>filterdiff</command>'s <option
1251 role="cmd-opt-filterdiff">-i</option> and <option
1252 role="cmd-opt-filterdiff">-x</option> options to choose the
1253 modifications to snip out of one patch, concatenating its
1254 output onto the end of the patch you want to merge into. You
1255 usually won't need to modify the patch you've merged the
1256 changes from. Instead, MQ will report some rejected hunks
1257 when you <command role="hg-ext-mq">qpush</command> it (from
1258 the hunks you moved into the other patch), and you can simply
1259 <command role="hg-ext-mq">qrefresh</command> the patch to drop
1260 the duplicate hunks.</para>
1262 <para id="x_441">If you have a patch that has multiple hunks modifying a
1263 file, and you only want to move a few of those hunks, the job
1264 becomes more messy, but you can still partly automate it. Use
1265 <command>lsdiff -nvv</command> to print some metadata about
1266 the patch.</para>
1268 &interaction.mq.tools.lsdiff;
1270 <para id="x_442">This command prints three different kinds of
1271 number:</para>
1272 <itemizedlist>
1273 <listitem><para id="x_443">(in the first column) a <emphasis>file
1274 number</emphasis> to identify each file modified in the
1275 patch;</para>
1276 </listitem>
1277 <listitem><para id="x_444">(on the next line, indented) the line number
1278 within a modified file where a hunk starts; and</para>
1279 </listitem>
1280 <listitem><para id="x_445">(on the same line) a <emphasis>hunk
1281 number</emphasis> to identify that hunk.</para>
1282 </listitem></itemizedlist>
1284 <para id="x_446">You'll have to use some visual inspection, and reading of
1285 the patch, to identify the file and hunk numbers you'll want,
1286 but you can then pass them to to
1287 <command>filterdiff</command>'s <option
1288 role="cmd-opt-filterdiff">--files</option> and <option
1289 role="cmd-opt-filterdiff">--hunks</option> options, to
1290 select exactly the file and hunk you want to extract.</para>
1292 <para id="x_447">Once you have this hunk, you can concatenate it onto the
1293 end of your destination patch and continue with the remainder
1294 of <xref linkend="sec:mq:combine"/>.</para>
1296 </sect2>
1297 </sect1>
1298 <sect1>
1299 <title>Differences between quilt and MQ</title>
1301 <para id="x_448">If you are already familiar with quilt, MQ provides a
1302 similar command set. There are a few differences in the way
1303 that it works.</para>
1305 <para id="x_449">You will already have noticed that most quilt commands have
1306 MQ counterparts that simply begin with a
1307 <quote><literal>q</literal></quote>. The exceptions are quilt's
1308 <literal>add</literal> and <literal>remove</literal> commands,
1309 the counterparts for which are the normal Mercurial <command
1310 role="hg-cmd">hg add</command> and <command role="hg-cmd">hg
1311 remove</command> commands. There is no MQ equivalent of the
1312 quilt <literal>edit</literal> command.</para>
1314 </sect1>
1315 </chapter>
1317 <!--
1318 local variables:
1319 sgml-parent-document: ("00book.xml" "book" "chapter")
1320 end:
1321 -->