diff ja/undo.tex @ 308:dd775100013d

more undo.tex

--- a/ja/undo.tex	Tue Feb 12 06:09:08 2008 +0900
+++ b/ja/undo.tex	Tue Feb 12 14:42:07 2008 +0900
@@ -866,21 +866,33 @@
 $BNc$($P!$%A%'%s%8%;%C%H$r<B:]$K%3%s%Q%$%k$9$kJQ99E~Ce%U%C%/$O!$ITCm0U$K$h(B
 $B$k%S%k%IITG=$rKI$0$3$H$,$G$-$k!%(B
 
-\section{Finding the source of a bug}
+%\section{Finding the source of a bug}
+\section{$B%P%0$N860x$r8+$D$1$k(B}
 \label{sec:undo:bisect}
 
-While it's all very well to be able to back out a changeset that
-introduced a bug, this requires that you know which changeset to back
-out.  Mercurial provides an invaluable command, called
-\hgcmd{bisect}, that helps you to automate this process and accomplish
-it very efficiently.
+%While it's all very well to be able to back out a changeset that
+%introduced a bug, this requires that you know which changeset to back
+%out.  Mercurial provides an invaluable command, called
+%\hgcmd{bisect}, that helps you to automate this process and accomplish
+%it very efficiently.
+
+$B%P%0$rH/@8$5$;$?%A%'%s%8%;%C%H$r%P%C%/%"%&%H$9$k$?$a$K$O!$$I$N%A%'%s%8%;%C(B
+$B%H$G%P%0$N:.F~$,5/$-$?$N$+$rCN$i$M$P$J$i$J$$!%(BMercurial$B$O(B\hgcmd{bisect}
+$B$H$$$&M-MQ$J%3%^%s%I$rDs6!$7$F$*$j!$$3$l$K$h$C$F%A%'%s%8%;%C%H$NFCDj$r<+(B
+$BF02=$7!$%P%C%/%"%&%H$r6K$a$F8z2LE*$K9T$&$3$H$,$G$-$k!%(B
 
-The idea behind the \hgcmd{bisect} command is that a changeset has
-introduced some change of behaviour that you can identify with a
-simple binary test.  You don't know which piece of code introduced the
-change, but you know how to test for the presence of the bug.  The
-\hgcmd{bisect} command uses your test to direct its search for the
-changeset that introduced the code that caused the bug.
+%The idea behind the \hgcmd{bisect} command is that a changeset has
+%introduced some change of behaviour that you can identify with a
+%simple binary test.  You don't know which piece of code introduced the
+%change, but you know how to test for the presence of the bug.  The
+%\hgcmd{bisect} command uses your test to direct its search for the
+%changeset that introduced the code that caused the bug.
+
+\hgcmd{bisect}$B%3%^%s%I$NGX8e$K$O!$%A%'%s%8%;%C%H$K$h$C$FC1=c$J%P%$%J%j%F(B
+$B%9%H$G==J,<1JL2DG=$J5sF0$NJQ2=$,@8$l$k$H$$$&9M$(J}$,$"$k!%$"$J$?$O$I$N%3!<(B
+$B%I$,JQ2=$r0z$-5/$3$7$?$N$+$O$o$+$i$J$$$,!$%P%0$,5/$-$F$$$k$+$r%F%9%H$9$k(B
+$BJ}K!$OCN$C$F$$$k!%(B\hgcmd{bisect}$B%3%^%s%I$O!$%F%9%H$K$h$C$F%P%0$r0z$-5/$3(B
+$B$7$?%A%'%s%8%;%C%H$rFCDj$9$k!%(B
 
 Here are a few scenarios to help you understand how you might apply
 this command.
@@ -904,6 +916,8 @@
   you build your project.
 \end{itemize}
 
+
+
 From these examples, it should be clear that the \hgcmd{bisect}
 command is not useful only for finding the sources of bugs.  You can
 use it to find any ``emergent property'' of a repository (anything