changeset 359:81116699a510

finished hgext.tex
author Yoshiki Yazawa <yaz@honeyplanet.jp>
date Wed, 03 Sep 2008 15:23:41 +0900
parents 1348ce7d2d77
children 45ad9986748a
files ja/hgext.tex ja/todo.txt
diffstat 2 files changed, 214 insertions(+), 100 deletions(-) [+]
line wrap: on
line diff
--- a/ja/hgext.tex	Tue Sep 02 19:03:38 2008 +0900
+++ b/ja/hgext.tex	Wed Sep 03 15:23:41 2008 +0900
@@ -212,6 +212,7 @@
 \texttt{python-inotify}$B$H$7$F%Q%C%1!<%82=$5$l$F$$$k!%$3$l$O%P%0$,Hs>o$KB?(B
 $B$/!$<BMQ$9$k$K$OHs8zN(E*$G$"$j!$;H$&$Y$-$G(B\emph{$B$J$$(B}$B!%(B
 \end{note}
+
 %To get going, it's best to already have a functioning copy of
 %Mercurial installed.
 $B@h$X?J$`$KEv$C$F!$@5$7$/5!G=$9$k(BMercurial$B$,%$%s%9%H!<%k$5$l$F$$$k$3$H$,(B
@@ -500,35 +501,59 @@
 %\subsection{Defining command aliases}
 \subsection{$B%3%^%s%I$N%(%$%j%"%9$r:n$k(B}
 
-It can be cumbersome to remember the options to both the
-\hgxcmd{extdiff}{extdiff} command and the diff viewer you want to use,
-so the \hgext{extdiff} extension lets you define \emph{new} commands
-that will invoke your diff viewer with exactly the right options.
+%It can be cumbersome to remember the options to both the
+%\hgxcmd{extdiff}{extdiff} command and the diff viewer you want to use,
+%so the \hgext{extdiff} extension lets you define \emph{new} commands
+%that will invoke your diff viewer with exactly the right options.
+
+\hgxcmd{extdiff}{extdiff}$B%3%^%s%I$H(Bdiff$B%S%e!<%"APJ}$N%*%W%7%g%s$r3P$($F$*(B
+$B$/$N$OLq2p$J$?$a!$(B\hgext{extdiff}$B3HD%$G(Bdiff$B%S%e!<%"$r@5$7$$%*%W%7%g%s$G5/(B
+$BF0$9$k(B\emph{$B?7$7$$(B}$B%3%^%s%I$rDj5A$9$k$3$H$,$G$-$k!%(B
 
-All you need to do is edit your \hgrc, and add a section named
-\rcsection{extdiff}.  Inside this section, you can define multiple
-commands.  Here's how to add a \texttt{kdiff3} command.  Once you've
-defined this, you can type ``\texttt{hg kdiff3}'' and the
-\hgext{extdiff} extension will run \command{kdiff3} for you.
+%All you need to do is edit your \hgrc, and add a section named
+%\rcsection{extdiff}.  Inside this section, you can define multiple
+%commands.  Here's how to add a \texttt{kdiff3} command.  Once you've
+%defined this, you can type ``\texttt{hg kdiff3}'' and the
+%\hgext{extdiff} extension will run \command{kdiff3} for you.
+
+$B$3$N$?$a$K$O(B\hgrc $B$rJT=8$7(B\rcsection{extdiff}$B$H$$$&L>A0$N?7$7$$%;%/%7%g%s(B
+$B$rDI2C$9$l$P$h$$!%$3$N%;%/%7%g%sFb$G$OJ#?t$N%3%^%s%I$rDj5A$9$k$3$H$,$G$-(B
+$B$k!%(B\texttt{kdiff3}$B%3%^%s%I$rDI2C$9$kJ}K!$rNc$H$7$F<($9!%0lEYDj5A$r9T$((B
+$B$P!$(B``\texttt{hg kdiff3}''$B$H%?%$%W$9$k$3$H$G(B\hgext{extdiff}$B3HD%$,(B
+\command{kdiff3}$B$r<B9T$9$k!%(B
+
 \begin{codesample2}
   [extdiff]
   cmd.kdiff3 =
 \end{codesample2}
-If you leave the right hand side of the definition empty, as above,
-the \hgext{extdiff} extension uses the name of the command you defined
-as the name of the external program to run.  But these names don't
-have to be the same.  Here, we define a command named ``\texttt{hg
-  wibble}'', which runs \command{kdiff3}.
+
+%If you leave the right hand side of the definition empty, as above,
+%the \hgext{extdiff} extension uses the name of the command you defined
+%as the name of the external program to run.  But these names don't
+%have to be the same.  Here, we define a command named ``\texttt{hg
+%  wibble}'', which runs \command{kdiff3}.
+
+$B>e$NNc$N$h$&$K1&JU$r6u$K$7$F$*$/$H!$(B\hgext{extdiff}$B3HD%$O30It$G5/F0$9$Y$-(B
+$B%3%^%s%IL>$H$7$FDj5A$rMQ$$$k!%$3$NL>A0$O=EJ#$7$F$O$J$i$J$$!%$3$3$G$O(B
+``\texttt{hg wibble}''$B$H$$$&L>A0$G%3%^%s%I(B\command{kdiff3}$B$r8F$S=P$9$rDj(B
+$B5A$7$F$$$k!%(B
+
 \begin{codesample2}
   [extdiff]
   cmd.wibble = kdiff3
 \end{codesample2}
 
-You can also specify the default options that you want to invoke your
-diff viewing program with.  The prefix to use is ``\texttt{opts.}'',
-followed by the name of the command to which the options apply.  This
-example defines a ``\texttt{hg vimdiff}'' command that runs the
-\command{vim} editor's \texttt{DirDiff} extension.
+%You can also specify the default options that you want to invoke your
+%diff viewing program with.  The prefix to use is ``\texttt{opts.}'',
+%followed by the name of the command to which the options apply.  This
+%example defines a ``\texttt{hg vimdiff}'' command that runs the
+%\command{vim} editor's \texttt{DirDiff} extension.
+
+diff$B%S%e!<%"$r5/F0$9$k:]$N%G%U%)%k%H%*%W%7%g%s$bDj5A$G$-$k!%Dj5A$G$O%*%W(B
+$B%7%g%s$rDj5A$7$?$$%3%^%s%I$NA0$K(B``\texttt{opts.}''$B$H$$$&@\F,<-$rIU$1$k!%(B
+$B$3$NNc$G$O(B\command{vim}$B%(%G%#%?$r(B\texttt{DirDiff}$B%*%W%7%g%sIU$-$G5/F0$9$k(B
+``\texttt{hg vimdiff}''$B%3%^%s%I$rDj5A$7$F$$$k!%(B
+
 \begin{codesample2}
   [extdiff]
   cmd.vimdiff = vim
@@ -546,105 +571,194 @@
 \section{\hgext{patchbomb}$B3HD%$K$h$C$FJQ99$r%a!<%k$9$k(B}
 \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.
+%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.
+
+$BB?$/$N%W%m%8%'%/%H$,(B``$B99?7$N%l%S%e!<(B''$B$NJ82=$r;}$C$F$$$k!%3+H/<T$?$A$O:G(B
+$B=*%P!<%8%g%s$r6&M-%j%]%8%H%j$K%3%_%C%H$9$kA0$K!$%Q%C%A$r::FI<TC#$,$$$k%a!<(B
+$B%j%s%0%j%9%H$XJQ99$rAw$j!$%A%'%C%/$d<u$1$?$j%3%a%s%H$rLc$C$?$j$9$k!%$$$/(B
+$B$D$+$N%W%m%8%'%/%H$G$OLgHV$N$h$&$J?M!9$r;}$C$F$$$?$j$5$($9$k!%H`$i$N;E;v(B
+$B$O!$?M!9$+$iAw$i$l$?JQ99$r!$H`$i0J30$K%"%/%;%98"$N$J$$%j%]%8%H%j$XE,MQ$9(B
+$B$k$3$H$G$"$k!%(B
 
-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''.
+%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.
+Mercurial$B$G$O(B\hgext{patchbomb}$B3HD%$rMQ$$$k$H%l%S%e!<$dE,MQ$N$?$a$KJQ99$r(B
+$B%a!<%k$GAw?.$9$k$3$H$,MF0W$K$J$k!%$3$N3HD%$NL>A0$OJQ99$r%Q%C%A$H$7$F%U%)!<(B
+$B%^%C%H$7!$(B1$B$D$N%A%'%s%8%;%C%HKh$K%a!<%k(B1$BDL$rAw?.$9$k$3$H$KM3Mh$9$k!%(B
+$B0lO"$NJQ99$rO"B3$7$F%a!<%k$GAw?.$9$k$3$H$r(B``$BGz7b(B''$B$K8+N)$F$F$$$k!%=>$C$F(B
+$B<u?.<T$,<u$1<h$k$N$O(B``$B%Q%C%AGzCF(B''$B$G$"$k!%(B
+
+%As usual, the basic configuration of the \hgext{patchbomb} extension
+%takes just one or two lines in your \hgrc.
+$BDL>o!$(B\hgext{patchbomb}$B3HD%$N4pK\@_Dj$O(B\hgrc $B$NCf$G(B1$B!$(B2$B9T$[$I$G$"$k!%(B
+
 \begin{codesample2}
   [extensions]
   patchbomb =
 \end{codesample2}
-Once you've enabled the extension, you will have a new command
-available, named \hgxcmd{patchbomb}{email}.
+%Once you've enabled the extension, you will have a new command
+%available, named \hgxcmd{patchbomb}{email}.
+
+$B3HD%$rM-8z$K$9$k$H!$(B\hgxcmd{patchbomb}{email}$B%3%^%s%I$,;H$($k$h$&$K$J$k!%(B
+
+%The safest and best way to invoke the \hgxcmd{patchbomb}{email}
+%command is to \emph{always} run it first with the
+%\hgxopt{patchbomb}{email}{-n} option.  This will show you what the
+%command \emph{would} send, without actually sending anything.  Once
+%you've had a quick glance over the changes and verified that you are
+%sending the right ones, you can rerun the same command, with the
+%\hgxopt{patchbomb}{email}{-n} option removed.
 
-The safest and best way to invoke the \hgxcmd{patchbomb}{email}
-command is to \emph{always} run it first with the
-\hgxopt{patchbomb}{email}{-n} option.  This will show you what the
-command \emph{would} send, without actually sending anything.  Once
-you've had a quick glance over the changes and verified that you are
-sending the right ones, you can rerun the same command, with the
-\hgxopt{patchbomb}{email}{-n} option removed.
+\hgxcmd{patchbomb}{email}$B$r5/F0$9$k$N$K:G$b0BA4$GNI$$J}K!$O!$$^$::G=i$K(B
+\hgxopt{patchbomb}{email}{-n}$B%*%W%7%g%s$rIU$1$F<B9T$7$F$_$k$3$H$@!%(B
+$B$3$l$K$h$j!$<B:]$NAw?.$O9T$o$:$K2?$,5/$-$k$N$+$r8+$k$3$H$,$G$-$k!%JQ99$K(B
+$BL\$rDL$7$F@5$7$$JQ99$rAw?.$9$k$3$H$r3NG'$G$-$?$i!$F1$8%3%^%s%I$r(B
+\hgxopt{patchbomb}{email}{-n}$B%*%W%7%g%s$J$7$G<B9T$9$k!%(B
 
-The \hgxcmd{patchbomb}{email} command accepts the same kind of
-revision syntax as every other Mercurial command.  For example, this
-command will send every revision between 7 and \texttt{tip},
-inclusive.
+%The \hgxcmd{patchbomb}{email} command accepts the same kind of
+%revision syntax as every other Mercurial command.  For example, this
+%command will send every revision between 7 and \texttt{tip},
+%inclusive.
+
+\hgxcmd{patchbomb}{email}$B%3%^%s%I$OB>$N(BMercurial$B%3%^%s%I$HF1MM$N%j%S%8%g(B
+$B%s;XDj9=J8$r<u$1IU$1$k!%Nc$($P%j%S%8%g%s(B7$B$+$i(Btip$B$^$G$r4^$`JQ99$rAw?.$9$k(B
+$B$J$I$N$h$&$K;XDj$,2DG=$G$"$k!%(B
 \begin{codesample2}
   hg email -n 7:tip
 \end{codesample2}
-You can also specify a \emph{repository} to compare with.  If you
-provide a repository but no revisions, the \hgxcmd{patchbomb}{email}
-command will send all revisions in the local repository that are not
-present in the remote repository.  If you additionally specify
-revisions or a branch name (the latter using the
-\hgxopt{patchbomb}{email}{-b} option), this will constrain the
-revisions sent.
+
+%You can also specify a \emph{repository} to compare with.  If you
+%provide a repository but no revisions, the \hgxcmd{patchbomb}{email}
+%command will send all revisions in the local repository that are not
+
+%present in the remote repository.  If you additionally specify
+%revisions or a branch name (the latter using the
+%\hgxopt{patchbomb}{email}{-b} option), this will constrain the
+%revisions sent.
+
+$BHf3SBP>]$H$7$F(B\emph{$B%j%]%8%H%j(B}$B$r;XDj$9$k$3$H$b$G$-$k!%%j%]%8%H%j$r;XDj(B
+$B$7!$%j%S%8%g%s$r;XDj$7$J$$>l9g!$(B\hgxcmd{patchbomb}{email}$B$O%m!<%+%k%j%]%8(B
+$B%H%j$K$"$C$F%j%b!<%H%j%]%8%H%j$K$J$$A4$F$N%P!<%8%g%s$rAw?.$9$k!%%j%S%8%g(B
+$B%s$^$?$O%V%i%s%AL>$r;XDj$9$k$H!J8e<T$O(B\hgxopt{patchbomb}{email}{-b}$B$rMQ$$(B
+$B$k!K!$Aw?.$5$l$k%j%S%8%g%s$K@)8B$,2C$o$k!%(B
 
-It's perfectly safe to run the \hgxcmd{patchbomb}{email} command
-without the names of the people you want to send to: if you do this,
-it will just prompt you for those values interactively.  (If you're
-using a Linux or Unix-like system, you should have enhanced
-\texttt{readline}-style editing capabilities when entering those
-headers, too, which is useful.)
+%It's perfectly safe to run the \hgxcmd{patchbomb}{email} command
+%without the names of the people you want to send to: if you do this,
+%it will just prompt you for those values interactively.  (If you're
+%using a Linux or Unix-like system, you should have enhanced
+%\texttt{readline}-style editing capabilities when entering those
+%headers, too, which is useful.)
+
+$BAw?.$7$?$$?MC#$NL>A0$r;XDj$;$:$K(B\hgxcmd{patchbomb}{email}$B%3%^%s%I$r;H$C$F(B
+$B$bA4$/0BA4$G$"$k!%$3$N>l9g!$BPOCE*$KF~NO$r5a$a$k!%(BLinux$B$^$?$O(BUnix$B7O$N%7%9(B
+$B%F%`$r;H$C$F$$$l$P!$%X%C%@$NF~NO$K;H$$$d$9$$(B\texttt{readline}$B%9%?%$%k$NJT(B
+$B=85!G=$rMxMQ$G$-$k(B
 
-When you are sending just one revision, the \hgxcmd{patchbomb}{email}
-command will by default use the first line of the changeset
-description as the subject of the single email message it sends.
+%When you are sending just one revision, the \hgxcmd{patchbomb}{email}
+%command will by default use the first line of the changeset
+%description as the subject of the single email message it sends.
+
+$B$?$@(B1$B$D$N%j%S%8%g%s$rAw$k>l9g!$(B\hgxcmd{patchbomb}{email}$B%3%^%s%I$O%G%U%)(B
+$B%k%H$G%A%'%s%8%;%C%H$N@bL@$N:G=i$N9T$r%a!<%k$N7oL>$H$7$FMQ$$$k!%(B
 
-If you send multiple revisions, the \hgxcmd{patchbomb}{email} command
-will usually send one message per changeset.  It will preface the
-series with an introductory message, in which you should describe the
-purpose of the series of changes you're sending.
+%If you send multiple revisions, the \hgxcmd{patchbomb}{email} command
+%will usually send one message per changeset.  It will preface the
+%series with an introductory message, in which you should describe the
+%purpose of the series of changes you're sending.
+
+$BJ#?t$N%j%S%8%g%s$rAw$k>l9g!$(B\hgxcmd{patchbomb}{email}$B%3%^%s%I$O(B1$B$D$N%A%'(B
+$B%s%8%;%C%HKh$K(B1$BDL$N%a!<%k$rAw?.$9$k!%3+;O$N%a!<%k$K$O0lO"$NJQ99$NL\E*$r5-(B
+$B=R$9$k@bL@J8$rIU$1$k!%(B
+
 
 %\subsection{Changing the behaviour of patchbombs}
 \subsection{patchbombs$B$N5sF0$rJQ99$9$k(B}
 
-Not every project has exactly the same conventions for sending changes
-in email; the \hgext{patchbomb} extension tries to accommodate a
-number of variations through command line options.
+%Not every project has exactly the same conventions for sending changes
+%in email; the \hgext{patchbomb} extension tries to accommodate a
+%number of variations through command line options.
+
+$BA4$F$N%W%m%8%'%/%H$,F1$8$h$&$J%a!<%k$K$h$kJQ99$NAwIU$N=,47$r;}$C$F$$$k$o(B
+$B$1$G$O$J$$!%(B\hgext{patchbomb}$B3HD%$O%3%^%s%I%i%$%s%*%W%7%g%s$GMM!9$JJ}K!(B
+$B$KBP1~$G$-$k$h$&$K$J$C$F$$$k!%(B
+
 \begin{itemize}
-\item You can write a subject for the introductory message on the
-  command line using the \hgxopt{patchbomb}{email}{-s} option.  This
-  takes one argument, the text of the subject to use.
-\item To change the email address from which the messages originate,
-  use the \hgxopt{patchbomb}{email}{-f} option.  This takes one
-  argument, the email address to use.
-\item The default behaviour is to send unified diffs (see
-  section~\ref{sec:mq:patch} for a description of the format), one per
-  message.  You can send a binary bundle instead with the
-  \hgxopt{patchbomb}{email}{-b} option.  
-\item Unified diffs are normally prefaced with a metadata header.  You
-  can omit this, and send unadorned diffs, with the
-  \hgxopt{patchbomb}{email}{--plain} option.
-\item Diffs are normally sent ``inline'', in the same body part as the
-  description of a patch.  This makes it easiest for the largest
-  number of readers to quote and respond to parts of a diff, as some
-  mail clients will only quote the first MIME body part in a message.
-  If you'd prefer to send the description and the diff in separate
-  body parts, use the \hgxopt{patchbomb}{email}{-a} option.
-\item Instead of sending mail messages, you can write them to an
-  \texttt{mbox}-format mail folder using the
-  \hgxopt{patchbomb}{email}{-m} option.  That option takes one
-  argument, the name of the file to write to.
-\item If you would like to add a \command{diffstat}-format summary to
-  each patch, and one to the introductory message, use the
-  \hgxopt{patchbomb}{email}{-d} option.  The \command{diffstat}
-  command displays a table containing the name of each file patched,
-  the number of lines affected, and a histogram showing how much each
-  file is modified.  This gives readers a qualitative glance at how
-  complex a patch is.
+%\item You can write a subject for the introductory message on the
+%  command line using the \hgxopt{patchbomb}{email}{-s} option.  This
+%  takes one argument, the text of the subject to use.
+ \item $B%3%^%s%I%i%$%s$+$i(B\hgxopt{patchbomb}{email}{-s}$B%*%W%7%g%s$r;H$C(B
+       $B$F!$@bL@J8$K$J$k7oL>$rF~NO$9$k$3$H$,$G$-$k!%$3$N%*%W%7%g%s$O7oL>$H(B
+       $B$7$F;H$o$l$k%F%-%9%H$r0z?t$H$7$F<h$k!%(B
+
+%\item To change the email address from which the messages originate,
+%  use the \hgxopt{patchbomb}{email}{-f} option.  This takes one
+%  argument, the email address to use.
+ \item $B%a%C%;!<%8$NAw?.85$N%"%I%l%9$rJQ99$9$k$K$O(B
+       \hgxopt{patchbomb}{email}{-f}$B%*%W%7%g%s$rMQ$$$k!%$3$N%*%W%7%g%s$O(B
+       $B%a!<%k%"%I%l%9$r0z?t$H$7$F<h$k!%(B
+
+%\item The default behaviour is to send unified diffs (see
+%  section~\ref{sec:mq:patch} for a description of the format), one per
+%  message.  You can send a binary bundle instead with the
+%  \hgxopt{patchbomb}{email}{-b} option.
+ \item $B%G%U%)%k%H$G$O(B1$B%a%C%;!<%8Kh$K(Bunified$B7A<0(Bdiff$B$rAw?.$9$k!%!J$3$N%U%)!<(B
+       $B%^%C%H$K$D$$$F$O(B\ref{sec:mq:patch}$B$r;2(B
+       $B>H!%!K(B\hgxopt{patchbomb}{email}{-b}$B%*%W%7%g%s$r;H$($P!$%P%$%J%j7A(B
+       $B<0$N%G!<%?$rE:IU$9$k$3$H$b$G$-$k!%(B
+
+%\item Unified diffs are normally prefaced with a metadata header.  You
+%  can omit this, and send unadorned diffs, with the
+%  \hgxopt{patchbomb}{email}{--plain} option.
+ \item unified$B7A<0(Bdiff$B$ODL>o%a%?%G!<%?$N%X%C%@$r;}(B
+       $B$D!%(B\hgxopt{patchbomb}{email}{--plain}$B%*%W%7%g%s$r;H$&$3$H$G$3$l(B
+       $B$r3d0&$9$k$3$H$,$G$-$k!%(B
+
+%\item Diffs are normally sent ``inline'', in the same body part as the
+%  description of a patch.  This makes it easiest for the largest
+%  number of readers to quote and respond to parts of a diff, as some
+%  mail clients will only quote the first MIME body part in a message.
+%  If you'd prefer to send the description and the diff in separate
+%  body parts, use the \hgxopt{patchbomb}{email}{-a} option.
+ \item $BDL>o!$:9J,$O%Q%C%A$N@bL@$HF1$8%\%G%#$NCf$K(B``$B%$%s%i%$%s(B''$B$G=q$-9~$^(B
+       $B$l$k!%$$$/$D$+$N%a!<%k%/%i%$%"%s%H$G$O:G=i$N(BMIME$B%Q!<%H$N$_$+$i0zMQ(B
+       $B$,2DG=$J$?$a!$$3$&$9$k$3$H$,:G$bB?$/$N?M$K$H$C$F%Q%C%A$NFCDj$NItJ,(B
+       $B$K%3%a%s%H$7$?$j$9$k$N$K9%ET9g$G$"$k!%@bL@J8$H(Bdiff$B$rJL$N%\%G%#%Q!<(B
+       $B%H$K$7$FAw?.$7$?$$>l9g$O(B\hgxopt{patchbomb}{email}{-a}$B%*%W%7%g%s$r(B
+       $B;H$&!%(B
+
+%\item Instead of sending mail messages, you can write them to an
+%  \texttt{mbox}-format mail folder using the
+%  \hgxopt{patchbomb}{email}{-m} option.  That option takes one
+%  argument, the name of the file to write to.
+ \item $B%a!<%k$G%a%C%;!<%8$rAw?.$9$kJQ$o$j(B
+       $B$K!$(B\hgxopt{patchbomb}{email}{-m}$B%*%W%7%g%s$r;H$C$F(B
+       \texttt{mbox}$B%U%)!<%^%C%H$G=PNO$5$;$k$3$H$b2DG=$@!%(B
+       $B$3$N%*%W%7%g%s$O=PNO%U%!%$%kL>$r0l$D%*%W%7%g%s$H$7$F<h$k!%(B
+
+%\item If you would like to add a \command{diffstat}-format summary to
+%  each patch, and one to the introductory message, use the
+%  \hgxopt{patchbomb}{email}{-d} option.  The \command{diffstat}
+%  command displays a table containing the name of each file patched,
+%  the number of lines affected, and a histogram showing how much each
+%  file is modified.  This gives readers a qualitative glance at how
+%  complex a patch is.
+ \item \command{diffstat}$B%U%)!<%^%C%H$N%5%^%j$r3F!9$N%Q%C%A$KIU$1!$@bL@J8(B
+       $B$rIU$1$?$$>l9g$O!$(B\hgxopt{patchbomb}{email}{-d}$B%*%W%7%g%s$r;H$&$H(B
+       $BNI$$!%(B\command{diffstat}$B%3%^%s%I$O%Q%C%A$5$l$?3F!9$N%U%!%$%kL>!$1F(B
+       $B6A$r<u$1$?9T?t!$3F%U%!%$%k$,$I$l$@$1JQ99$5$l$?$+$r<($9%R%9%H%0%i%`(B
+       $B$r$r4^$`%F!<%V%k$rI=<($9$k!%$3$N>pJs$O!$%Q%C%A$NJ#;($5$K$D$$$FDj@-(B
+       $BE*$JM}2r$rF@$k$N$KLrN)$D!%(B
+
 \end{itemize}
 
 %%% Local Variables:
--- a/ja/todo.txt	Tue Sep 02 19:03:38 2008 +0900
+++ b/ja/todo.txt	Wed Sep 03 15:23:41 2008 +0900
@@ -5,7 +5,7 @@
 daily.tex
 filenames.tex
 hg_id.tex	noneed
-hgext.tex	50%
+hgext.tex	100%
 hook.tex
 intro.tex
 license.tex