Re: [PATCH] git-bisect.sh: don't accidentally override existing branch "bisect"
- From
Christian Couder <chriscool@tuxfamily.org>
- Date
- May 1, 2008, 12:27 UTC
- Message-ID
- <200805011427.22901.chriscool@tuxfamily.org>
- In-Reply-To
- <cac9e4380805010515h783dcf74h39fcc522c78885d3@mail.gmail.com>
Le jeudi 1 mai 2008, Richard Quirk a écrit :
Show 16 quoted lines
> On Wed, Apr 30, 2008 at 11:30 PM, Christian Couder
>
> <chriscool@tuxfamily.org> wrote:
> > Minor nitpick: you may use:
> >
> > git show-ref -q {new-,}bisect
> >
> > instead of:
> >
> >
> > git show-ref bisect > /dev/null ||
> > git show-ref new-bisect > /dev/null
>
> Careful with that - it's a bashism and would fail if /bin/sh is dash.
> ie it would say that a branch called literally "{new-,}bisect" does
> not exist, even if new-bisect and bisect do.You are right. Thanks. So what about a plain:
git show-ref -q bisect new-bisect
Regards, Christian.