From: Jon Seymour <jon.seymour@gmail.com>
Date: Sat, 30 Jul 2011 13:58:16 GMT
Subject: Re: [PATCH 0/5] bisect: Add support for a --no-checkout option.
Message-ID: <CAH3Anrp8aT1UwfstJ99Ug4MD2CZKB9oE_oRLksbkGGE1xSELsg@mail.gmail.com>
In-Reply-To: <201107301548.09815.chriscool@tuxfamily.org>

On Sat, Jul 30, 2011 at 11:48 PM, Christian Couder
<chriscool@tuxfamily.org> wrote:
> Hi,
>
> On Saturday 30 July 2011 10:28:26 Jon Seymour wrote:
>> For some bisection tasks, checking out the commit at each stage of the
>> bisection process is unecessary or undesirable.
>>
>> This series adds support for a --no-checkout[=<ref>] option to git-bisect.
>
> Sorry but I didn't reply to your previous email when you asked about a "--no-
> checkout[=<ref>]" compromise. I thought that Junio would reply and then I
> forgot about it.
>
> My opinion is that if you really want to be able to use another ref, then
> there should be a special "--update-ref=<ref>" or "--use-ref=<ref>" option
> that is different from "--no-checkout".
>
> "--no-checkout" looks like a boolean argument. And "--no-checkout[=<ref>]" may
> make the user think that this option will not checkout <ref>, and then it
> leads to the confusing question "but why would it checkout this f&#@ing ref in
> the first place?".

Good suggestions.

So, to confirm that I understand:

    use --no-checkout to control (no-)checkout behaviour and
--update-ref to specify a ref other than HEAD?

jon.