hgbook
changeset 232:2469608b4a08
Start writing up the patchbomb extension.
author | Bryan O'Sullivan <bos@serpentine.com> |
---|---|
date | Sun May 27 09:40:12 2007 -0700 (2007-05-27) |
parents | 28ddbf9f3729 |
children | 696b1e0c01df |
files | en/hgext.tex |
line diff
1.1 --- a/en/hgext.tex Sun May 27 09:39:58 2007 -0700 1.2 +++ b/en/hgext.tex Sun May 27 09:40:12 2007 -0700 1.3 @@ -318,6 +318,37 @@ 1.4 opts.vimdiff = -f '+next' '+execute "DirDiff" argv(0) argv(1)' 1.5 \end{codesample2} 1.6 1.7 +\section{Cherrypicking changes with the \hgext{transplant} extension} 1.8 +\label{sec:hgext:transplant} 1.9 + 1.10 +Need to have a long chat with Brendan about this. 1.11 + 1.12 +\section{Send changes via email with the \hgext{patchbomb} extension} 1.13 +\label{sec:hgext:patchbomb} 1.14 + 1.15 +Many projects have a culture of ``change review'', in which people 1.16 +send their modifications to a mailing list for others to read and 1.17 +comment on before they commit the final version to a shared 1.18 +repository. Some projects have people who act as gatekeepers; they 1.19 +apply changes from other people to a repository to which those others 1.20 +don't have access. 1.21 + 1.22 +Mercurial makes it easy to send changes over email for review or 1.23 +application, via its \hgext{patchbomb} extension. The extension is so 1.24 +namd because changes are formatted as patches, and it's usual to send 1.25 +one changeset per email message. Sending a long series of changes by 1.26 +email is thus much like ``bombing'' the recipient's inbox, hence 1.27 +``patchbomb''. 1.28 + 1.29 +As usual, the basic configuration of the \hgext{patchbomb} extension 1.30 +takes just one or two lines in your \hgrc. 1.31 +\begin{codesample2} 1.32 + [extensions] 1.33 + patchbomb = 1.34 +\end{codesample2} 1.35 +Once you've enabled the extension, you will have a new command 1.36 +available, named \hgxcmd{email}. 1.37 + 1.38 1.39 %%% Local Variables: 1.40 %%% mode: latex