From: "H. Peter Anvin" <hpa@zytor.com>
To: Alex Henrie <alexhenrie24@gmail.com>,
Felipe Contreras <felipe.contreras@gmail.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git mailing list <git@vger.kernel.org>,
Josh Steadmon <steadmon@google.com>, Jeff King <peff@peff.net>,
Jeff Hostetler <jeffhost@microsoft.com>
Subject: Re: RFC: error codes on exit
Date: Fri, 21 May 2021 16:20:01 -0700 [thread overview]
Message-ID: <dc14c50d-c626-19f8-e615-52ca3c9051dc@zytor.com> (raw)
In-Reply-To: <CAMMLpeScunGg5WM4N90vG+yN3tOATqhsL2iRLsJ43ksNyTx_wQ@mail.gmail.com>
On 5/21/21 9:53 AM, Alex Henrie wrote:
> On Wed, May 19, 2021 at 6:40 PM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>>
>> It's good to not include many initial codes, but I would start with at
>> least three:
>>
>> OK = 0,
>> UNKNOWN = 1,
>> NORMAL = 2,
>
> If you go that route, could you please pick a word other than "normal"
> to describe errors that are not entirely unexpected? I'm worried that
> someone will see "normal" and use it instead of "OK" to indicate
> success.
>
<sysexits.h>
-hpa
next prev parent reply other threads:[~2021-05-21 23:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 23:34 RFC: error codes on exit Jonathan Nieder
2021-05-20 0:40 ` Felipe Contreras
2021-05-21 16:53 ` Alex Henrie
2021-05-21 23:20 ` H. Peter Anvin [this message]
2021-05-22 4:06 ` Bagas Sanjaya
2021-05-22 8:49 ` Junio C Hamano
2021-05-22 9:08 ` H. Peter Anvin
2021-05-22 21:22 ` Felipe Contreras
2021-05-22 21:29 ` H. Peter Anvin
2021-05-22 21:53 ` Felipe Contreras
2021-05-22 23:02 ` H. Peter Anvin
2021-05-22 9:12 ` Philip Oakley
2021-05-22 21:19 ` Felipe Contreras
2021-05-25 17:24 ` Alex Henrie
2021-05-25 18:43 ` Felipe Contreras
2021-05-20 0:49 ` Junio C Hamano
2021-05-20 1:19 ` Felipe Contreras
2021-05-20 1:55 ` Jonathan Nieder
2021-05-20 2:28 ` Junio C Hamano
2021-05-20 13:28 ` Jeff King
2021-05-20 17:47 ` Jonathan Nieder
2021-05-21 9:43 ` Jeff King
2021-05-20 15:09 ` Jeff Hostetler
2021-05-21 1:33 ` brian m. carlson
2021-05-21 1:20 ` brian m. carlson
2021-05-26 8:21 ` Ævar Arnfjörð Bjarmason
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=dc14c50d-c626-19f8-e615-52ca3c9051dc@zytor.com \
--to=hpa@zytor.com \
--cc=alexhenrie24@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=jeffhost@microsoft.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
--cc=steadmon@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.