git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tom Prince <tom.prince@ualberta.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Bisect run: "skip" current commit if script exit code is 125.
Date: Fri, 26 Oct 2007 23:12:09 -0700	[thread overview]
Message-ID: <7vabq5ulvq.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20071027053305.GB3115@hermes.priv> (Tom Prince's message of "Sat, 27 Oct 2007 01:33:06 -0400")

Tom Prince <tom.prince@ualberta.net> writes:

> On Sat, Oct 27, 2007 at 07:02:31AM +0200, Christian Couder wrote:
>> Le vendredi 26 octobre 2007, Benoit SIGOURE a écrit :
>> > On Oct 26, 2007, at 5:39 AM, Christian Couder wrote:
>> > >
>> > > +The special exit code 125 should be used when the current source code
>> > > +cannot be tested. If the "run" script exits with this code, the
>> > > current
>> > > +revision will be "skip"ped, see `git bisect skip` above.
>> > > [...]
>> >
>> Also there is:
>> 
>> $ grep 77 /usr/include/sysexits.h
>> #define EX_NOPERM       77      /* permission denied */
>
> How about 
>
> #define EX_TEMPFAIL     75      /* temp failure; user is invited to retry */

Let's stop bikeshedding.  125 is as good as anything else.

      reply	other threads:[~2007-10-27  6:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  3:39 [PATCH] Bisect run: "skip" current commit if script exit code is 125 Christian Couder
2007-10-26  6:25 ` Benoit SIGOURE
2007-10-27  5:02   ` Christian Couder
     [not found]     ` <20071027052834.GA3115@hermes.priv>
2007-10-27  5:33       ` Tom Prince
2007-10-27  6:12         ` Junio C Hamano [this message]

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=7vabq5ulvq.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tom.prince@ualberta.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).