[prev in list] [next in list] [prev in thread] [next in thread] 

List:       git
Subject:    Re: [PATCH v8 0/7] bisect: Add support for --no-checkout and
From:       Jon Seymour <jon.seymour () gmail ! com>
Date:       2011-07-31 13:26:18
Message-ID: CAH3AnroWm-BU1svjJqK3WzoNknWk495AJ0mxwWMq+1sgAxxnPg () mail ! gmail ! com
[Download RAW message or body]

On Sun, Jul 31, 2011 at 9:55 PM, Jon Seymour <jon.seymour@gmail.com> wrote:
>
> For example:
>
>        git bisect run eval '
>                rc=1;
>                if git rev-list --objects HEAD >tmp.$$; then
>                   git pack-objects --stdout >/dev/null < tmp.$$ && rc=0;
>                fi;
>                rm tmp.$$;
>                test $rc -eq 0;'
>

Sverre has pointed out I screwed the example up again. It should have been:

git bisect start HEAD <some-known-good-commit> <boundary-commits> --no-checkout
git bisect run eval '
               rc=1;
               if git rev-list --objects HEAD >tmp.$$; then
                  git pack-objects --stdout >/dev/null < tmp.$$ && rc=0;
               fi;
               rm tmp.$$;
               test $rc -eq 0;'

I think the examples in the documentation and test are correct (modulo
an accurate description of what good choices for <boundary-commit>'s
are).

jon.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]