From: Christian Couder <chriscool@tuxfamily.org>
To: "Richard Quirk" <richard.quirk@gmail.com>
Cc: "Gerrit Pape" <pape@smarden.org>,
git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [PATCH] git-bisect.sh: don't accidentally override existing branch "bisect"
Date: Thu, 1 May 2008 14:27:22 +0200 [thread overview]
Message-ID: <200805011427.22901.chriscool@tuxfamily.org> (raw)
In-Reply-To: <cac9e4380805010515h783dcf74h39fcc522c78885d3@mail.gmail.com>
Le jeudi 1 mai 2008, Richard Quirk a écrit :
> 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.
next prev parent reply other threads:[~2008-05-01 12:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 16:46 [PATCH] git-bisect.sh: don't accidentally override existing branch "bisect" Gerrit Pape
2008-04-30 21:30 ` Christian Couder
2008-05-01 12:15 ` Richard Quirk
2008-05-01 12:27 ` Christian Couder [this message]
2008-05-02 8:56 ` [PATCH amend] " Gerrit Pape
2008-05-03 8:42 ` Christian Couder
2008-05-05 7:43 ` Gerrit Pape
2008-05-06 6:20 ` Christian Couder
2008-05-02 8:22 ` [PATCH] " Karl Hasselström
2008-05-02 17:38 ` Junio C Hamano
2008-05-03 12:48 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200805011427.22901.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.org \
--cc=richard.quirk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).