# HG changeset patch
# User Bryan O'Sullivan <bos@serpentine.com>
# Date 1180284012 25200
# Node ID 2469608b4a08f428b33045eb85ce07736b24f25c
# Parent  28ddbf9f3729c5b4e1b70cc2f7dc0a2e532fc932
Start writing up the patchbomb extension.

diff -r 28ddbf9f3729 -r 2469608b4a08 en/hgext.tex
--- a/en/hgext.tex	Sun May 27 09:39:58 2007 -0700
+++ b/en/hgext.tex	Sun May 27 09:40:12 2007 -0700
@@ -318,6 +318,37 @@
   opts.vimdiff = -f '+next' '+execute "DirDiff" argv(0) argv(1)'
 \end{codesample2}
 
+\section{Cherrypicking changes with the \hgext{transplant} extension}
+\label{sec:hgext:transplant}
+
+Need to have a long chat with Brendan about this.
+
+\section{Send changes via email with the \hgext{patchbomb} extension}
+\label{sec:hgext:patchbomb}
+
+Many projects have a culture of ``change review'', in which people
+send their modifications to a mailing list for others to read and
+comment on before they commit the final version to a shared
+repository.  Some projects have people who act as gatekeepers; they
+apply changes from other people to a repository to which those others
+don't have access.
+
+Mercurial makes it easy to send changes over email for review or
+application, via its \hgext{patchbomb} extension.  The extension is so
+namd because changes are formatted as patches, and it's usual to send
+one changeset per email message.  Sending a long series of changes by
+email is thus much like ``bombing'' the recipient's inbox, hence
+``patchbomb''.
+
+As usual, the basic configuration of the \hgext{patchbomb} extension
+takes just one or two lines in your \hgrc.
+\begin{codesample2}
+  [extensions]
+  patchbomb =
+\end{codesample2}
+Once you've enabled the extension, you will have a new command
+available, named \hgxcmd{email}.
+
 
 %%% Local Variables: 
 %%% mode: latex