From: Junio C Hamano <gitster@pobox.com>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Christian Couder <chriscool@tuxfamily.org>
Subject: Re: git bisect code 125 - "WFT?"
Date: Wed, 16 Mar 2011 14:36:38 -0700 [thread overview]
Message-ID: <7v1v267no9.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTikZ3Po-YdhO-qCn5usVkt4J196eFF6YdbAeMG_X@mail.gmail.com> (Piotr Krukowiecki's message of "Wed, 16 Mar 2011 21:44:03 +0100")
Piotr Krukowiecki <piotr.krukowiecki@gmail.com> writes:
> Opinions? Would it be possible to change the meaning of the codes now
> (in 1.8.0)?
How about just documenting why it is a bad idea to use 126 or 127 as you
found out somewhere, and stopping there, iow, without changing the code to
use 126/127 that we consider it is a bad idea to use and avoided using so
far?
next prev parent reply other threads:[~2011-03-16 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 20:44 git bisect code 125 - "WFT?" Piotr Krukowiecki
2011-03-16 21:36 ` Junio C Hamano [this message]
2011-03-16 22:06 ` Piotr Krukowiecki
2011-03-17 6:55 ` Johannes Sixt
2011-03-17 7:27 ` Jeff King
2011-03-17 17:56 ` Junio C Hamano
2011-03-19 15:18 ` [PATCH 1/2] git bisect run: exit code 126 and 127 abort the run Piotr Krukowiecki
2011-03-19 15:20 ` [PATCH 2/2] bisect documentation: exit codes 126,127 abort bisect Piotr Krukowiecki
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=7v1v267no9.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=piotr.krukowiecki@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).