From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Bisect: add checks at the beginning of "git bisect run".
Date: Tue, 27 Mar 2007 09:15:12 +0200 [thread overview]
Message-ID: <200703270915.12408.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vzm5zs1aq.fsf@assigned-by-dhcp.cox.net>
Le mardi 27 mars 2007 07:28, Junio C Hamano a écrit :
> Christian Couder <chriscool@tuxfamily.org> writes:
> >
> > bisect_run () {
> > + # Check that we have everything to run correctly.
> > + test -d "$GIT_DIR/refs/bisect" || {
> > + echo >&2 'You need to start by "git bisect start".'
> > + echo >&2 'And then by "git bisect bad" and "git bisect good".'
> > + exit 1
> > + }
> > + bisect_next_check fail
> > +
>
> I think you shouldn't need the first "test -d blah"; doesn't
> "bisect_next_check fail" already give that message?
Without the first "test -d blah", if "bisect start" was not already used,
then the user will only see :
'You need to give me at least one good and one bad revisions.'
And then when using "git bisect good" or "git bisect bad" to give good or
bad revision:
'You need to start by "git bisect start"
Do you want me to do it for you [Y/n]?'
So I thought that it would be better to tell the user upfront everything
that should be done.
But it's up to you.
Thanks,
Christian.
next prev parent reply other threads:[~2007-03-27 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 4:49 [PATCH] Bisect: add checks at the beginning of "git bisect run" Christian Couder
2007-03-27 5:28 ` Junio C Hamano
2007-03-27 7:15 ` Christian Couder [this message]
2007-03-27 7:22 ` Junio C Hamano
2007-03-27 5:46 ` Junio C Hamano
2007-03-28 3:44 ` Christian Couder
2007-03-28 5:46 ` Junio C Hamano
2007-03-28 7:52 ` Christian Couder
2007-03-28 7:57 ` Junio C Hamano
2007-03-29 5:02 ` Christian Couder
2007-03-29 6:06 ` Junio C Hamano
2007-04-05 8:01 ` Christian Couder
2007-04-05 8:05 ` Christian Couder
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=200703270915.12408.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).