From: Christian Couder <chriscool@tuxfamily.org>
Date: Sat, 30 Jul 2011 14:19:50 GMT
Subject: Re: [PATCH 0/5] bisect: Add support for a --no-checkout option.
Message-ID: <201107301619.51438.chriscool@tuxfamily.org>
In-Reply-To: <CAH3Anrp8aT1UwfstJ99Ug4MD2CZKB9oE_oRLksbkGGE1xSELsg@mail.gmail.com>

On Saturday 30 July 2011 15:58:16 Jon Seymour wrote:
> On Sat, Jul 30, 2011 at 11:48 PM, Christian Couder wrote:
> > 
> > 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?

Yeah, I think it would be less confusing like this.

Thanks,
Christian.