hgbook is broken?

KIMURA Masaru hiyuh.root at gmail.com
Wed Jan 28 04:33:52 UTC 2009


Hi,

Thank you, Arne.
BTW, how can we remind this author (maby, Bryan?) for sure?
Broken document is too much to tolerate (at least for me).

2009/1/21 Arne Babenhauserheide <arne_bab at web.de>:
> Hi,
>
> I don't know how to test this fix, but I hope that the following diff does the
> trick:
>
> ######################## ########################
> # HG changeset patch
> # User Arne Babenhauserheide <bab at draketo.de>
> # Date 1232543798 -3600
> # Node ID 91adcea08b33fd2584c7803360accf0373a0f188
> # Parent  97e929385442d9f39f6a5abc796f2d2156f35201
> Fix the bisect section, I hope (bisect is now part of Mercurial).
>
> diff --git a/en/examples/bisect b/en/examples/bisect
> --- a/en/examples/bisect
> +++ b/en/examples/bisect
> @@ -1,7 +1,8 @@
>  #!/bin/bash
>
> -echo '[extensions]' >> $HGRC
> -echo 'hbisect =' >> $HGRC
> +# Don't add the bisect extension. That's not needed anymore.
> +#echo '[extensions]' >> $HGRC
> +#echo 'hbisect =' >> $HGRC
>
>  # XXX There's some kind of horrible nondeterminism in the execution of
>  # bisect at the moment.  Ugh.
> diff --git a/en/undo.tex b/en/undo.tex
> --- a/en/undo.tex
> +++ b/en/undo.tex
> @@ -569,7 +569,6 @@ Here's an example of \hgcmd{bisect} in a
>
>  Now let's create a repository, so that we can try out the
>  \hgcmd{bisect} command in isolation.
> -\interaction{bisect.init}
>  We'll simulate a project that has a bug in it in a simple-minded way:
>  create trivial changes in a loop, and nominate one specific change
>  that will have the ``bug''.  This loop creates 35 changesets, each
> ######################## ########################
>
>
> Am Samstag 17 Januar 2009 11:58:59 schrieb KIMURA Masaru:
>> Hi,
>>
>> can someone fix this "hbisect" breakage?
>> http://hgbook.red-bean.com/hgbookch9.html#x13-1880009.5
>>
>> THX



More information about the Mercurial mailing list