From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS53758 23.128.96.0/24 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 7B69A1F5AE for ; Tue, 25 May 2021 17:25:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234001AbhEYR0Y (ORCPT ); Tue, 25 May 2021 13:26:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233896AbhEYR0T (ORCPT ); Tue, 25 May 2021 13:26:19 -0400 Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1C458C061574 for ; Tue, 25 May 2021 10:24:49 -0700 (PDT) Received: by mail-lf1-x12f.google.com with SMTP id r5so47239083lfr.5 for ; Tue, 25 May 2021 10:24:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2Ihvgpv9KFvdCrH6yPdEyN1mfLCm5YZXFX/fjjksKnk=; b=mI2hZ/JIFM31Y6z1lq/wimij+R2QG3hhMRm7OxCRZY4CROVI08dSPY7sY1AE6vgqNC CmCARQmtptyLKoppbsVxRfeVNbCEUPlsWTxEOymXHIjJBD/4UWJwFYbrGDtuGpfRkFPH d6KKA5UUoxP2dWZ7tIPOcD9rPtj2eTsgnN7qaSGwMIH0FvxXZj6zJk3I9p8/TMwyrtuS XHOfIDIQm3pcuQu0Er47vDSyEW1gFqpILlZsfVagHwdX3tTrEFlC9X5U3CtqWVDw4PVP VdfnHTyWeaDu+Su8+AyDcy4YUFIyNod57SuXt1jl1lnrJVwvyYcquPlHe/+CeE5gPjtc s9+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2Ihvgpv9KFvdCrH6yPdEyN1mfLCm5YZXFX/fjjksKnk=; b=JJi7qN+slclEaEullcNF0FCsfABMziQEzV/1v799pRAubkzE9UFznIM/exaGKybrIa i1DQIDboAVoHgFyqkrtfjFbUNalLParY0LzhcgwfJvl+uL1boei1m3upuHlSSpC0u7Du 53B2xH9zMB9I5uyMNZ732vXRTtmjKroxmk0/5cmojgo16jSPoGYOlLvrgmomHDny6O74 TnOk5gq4+VnI3/C7rQlNo1jzDibUuIAETdwVuZo/8xyCP254Lp5EogvDXATH2kg59tks vClk3I///SNxetaSN83JNXmZPMtqwAu4cA1aZJgfFwIXgwzLtTb6TFrbk9cprFyGBLHs EH/A== X-Gm-Message-State: AOAM532iP8ONLkftD7aDBUvqcaEpSxphzjD1jQ2rdHfckvFHlpmQv1C9 RiYmztPLzRjgxWrwZsUEQpWcLzBBAo/dFD6ilaZ7MBTjABc= X-Google-Smtp-Source: ABdhPJyCZWqbxvlxEDBQt4zbVJk8s8m9hSI2AAA+ofk+lu3fcLyYQCKaYrBZanm72CLf4xymgxchgMvaTUy4xNGX8hI= X-Received: by 2002:a05:6512:3990:: with SMTP id j16mr14577815lfu.367.1621963486799; Tue, 25 May 2021 10:24:46 -0700 (PDT) MIME-Version: 1.0 References: <60a5afeeb13b4_1d8f2208a5@natae.notmuch> <7f0c9ab8-c1ca-171b-8247-6d921702f3bc@iee.email> <60a97550287b3_857e9208b8@natae.notmuch> In-Reply-To: <60a97550287b3_857e9208b8@natae.notmuch> From: Alex Henrie Date: Tue, 25 May 2021 11:24:35 -0600 Message-ID: Subject: Re: RFC: error codes on exit To: Felipe Contreras Cc: Philip Oakley , Jonathan Nieder , Git mailing list , Josh Steadmon , Jeff King , Jeff Hostetler Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sat, May 22, 2021 at 3:19 PM Felipe Contreras wrote: > > Philip Oakley wrote: > > On 21/05/2021 17:53, Alex Henrie wrote: > > > On Wed, May 19, 2021 at 6:40 PM Felipe Contreras > > > 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. > > > > > > -Alex > > Typical <== Normal > > > > Though abnormal and atypical often have different implications ;-) > > P. > > Or USUAL. The words "typical" and "usual" have the same problem of making it sound like there was no error. I would suggest terms like "user error", "network error", etc. instead. -Alex