# HG changeset patch # User Bryan O'Sullivan # Date 1167343823 28800 # Node ID 153efeaa8f57a00de099a5677816a7b4b9946067 # Parent 26b7a4e943aa22bb75491c5b69365cae603f74bf Fix stupid build bugs. diff -r 26b7a4e943aa -r 153efeaa8f57 en/Makefile --- a/en/Makefile Thu Dec 28 14:06:15 2006 -0800 +++ b/en/Makefile Thu Dec 28 14:10:23 2006 -0800 @@ -49,6 +49,7 @@ example-sources := \ backout \ + bisect \ daily.copy \ daily.files \ daily.rename \ diff -r 26b7a4e943aa -r 153efeaa8f57 en/examples/bisect --- a/en/examples/bisect Thu Dec 28 14:06:15 2006 -0800 +++ b/en/examples/bisect Thu Dec 28 14:10:23 2006 -0800 @@ -51,7 +51,7 @@ echo this revision is $result hg bisect $result -#$ name: mytest +#$ name: search.mytest mytest() { if grep -q 'i have a gub' * diff -r 26b7a4e943aa -r 153efeaa8f57 en/undo.tex --- a/en/undo.tex Thu Dec 28 14:06:15 2006 -0800 +++ b/en/undo.tex Thu Dec 28 14:10:23 2006 -0800 @@ -620,17 +620,17 @@ \command{grep} command to see if our ``bad'' file is present in the working directory. If it is, this revision is bad; if not, this revision is good. -\interaction{search.step1} +\interaction{bisect.search.step1} This test looks like a perfect candidate for automation, so let's turn it into a shell function. -\interaction{search.mytest} +\interaction{bisect.search.mytest} We can now run an entire test step with a single command, \texttt{mytest}. -\interaction{search.step2} +\interaction{bisect.search.step2} A few more invocations of our canned test step command, and we're done. -\interaction{search.rest} +\interaction{bisect.search.rest} Even though we had~40 changesets to search through, the \hgext{bisect} extension let us find the changeset that introduced our ``bug'' with @@ -647,7 +647,7 @@ doesn't use much space, so it doesn't matter if you forget to run this command. However, \hgext{bisect} won't let you start a new search in that repository until you do a \hgcmdargs{bisect}{reset}. -\interaction{search.reset} +\interaction{bisect.search.reset} \section{Tips for finding bugs effectively}