From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: "Santi Béjar" <sbejar@gmail.com>, git@vger.kernel.org
Subject: Re: [RFC/PATCH] git-what: explain what to do next
Date: Wed, 28 May 2008 22:09:46 -0700 [thread overview]
Message-ID: <7vlk1tpug5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200805290639.38134.chriscool@tuxfamily.org> (Christian Couder's message of "Thu, 29 May 2008 06:39:38 +0200")
Christian Couder <chriscool@tuxfamily.org> writes:
> It seems not very friendly to just "return 1" when not bisecting.
> And before my last patch to use BISECT_START to check if we are bisecting,
> it would perhaps have been better to use 'test -f "$GIT_DIR/BISECT_NAMES"'.
The reason for this silence is because Santi wants to call potential
culprits in turn and stop when one responds "Yeah, I am the guilty one who
threw a monkey wrench into the user's workflow". For that to work, "No,
the user is not in the middle of any interaction with me" response needs
to be silent.
next prev parent reply other threads:[~2008-05-29 5:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 8:34 [RFC/PATCH] git-what: explain what to do next Santi Béjar
2008-05-27 10:53 ` Johannes Schindelin
2008-05-27 12:58 ` Santi Béjar
2008-05-27 13:12 ` Johannes Schindelin
2008-05-27 13:37 ` Santi Béjar
2008-05-27 13:52 ` Stephen R. van den Berg
2008-05-27 14:21 ` Santi Béjar
2008-05-27 18:08 ` Steven Walter
2008-05-27 20:24 ` Junio C Hamano
2008-05-27 20:51 ` Junio C Hamano
2008-05-28 9:12 ` Santi Béjar
2008-05-29 4:39 ` Christian Couder
2008-05-29 5:09 ` Junio C Hamano [this message]
2008-05-29 14:56 ` Jon Loeliger
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=7vlk1tpug5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=sbejar@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).