git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Bert Wesarg <bert.wesarg@googlemail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH] remote: add meaningful exit code on missing/existing
Date: Mon, 26 Oct 2020 20:55:36 +0100	[thread overview]
Message-ID: <CAKPyHN0Dbk+fqYR-5-RMUanJXFqjzh_w6zd0QXnM1fMpSUDJ3Q@mail.gmail.com> (raw)
In-Reply-To: <20201026144825.26537-1-avarab@gmail.com>

On Mon, Oct 26, 2020 at 3:48 PM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> diff --git a/Documentation/git-remote.txt b/Documentation/git-remote.txt
> index 9659abbf8e..c1f1355f52 100644
> --- a/Documentation/git-remote.txt
> +++ b/Documentation/git-remote.txt
> @@ -203,6 +203,17 @@ The remote configuration is achieved using the `remote.origin.url` and
>  `remote.origin.fetch` configuration variables.  (See
>  linkgit:git-config[1]).
>
> +EXIT STATUS
> +-----------
> +
> +On success, the exit status is `0`.
> +
> +When subcommands such as 'add', 'rename' and 'remove' can't find the

at least a comma before 'and', but I consider 'or' better here anyway:

When subcommands such as 'add', 'rename', or 'remove' can't find the

Bert

> +remote in question the exit status is `2`, when the remote already
> +exists the exit status is `3`.
> +
> +On any other error, the exit status may be any other non-zero value.
> +
>  EXAMPLES
>  --------
>

      parent reply	other threads:[~2020-10-26 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 14:48 [PATCH] remote: add meaningful exit code on missing/existing Ævar Arnfjörð Bjarmason
2020-10-26 14:52 ` Eric Sunshine
2020-10-26 18:29 ` Junio C Hamano
2020-10-26 19:45 ` Jeff King
2020-10-26 21:00   ` Junio C Hamano
2020-10-27  9:41     ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2020-10-26 19:55 ` Bert Wesarg [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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKPyHN0Dbk+fqYR-5-RMUanJXFqjzh_w6zd0QXnM1fMpSUDJ3Q@mail.gmail.com \
    --to=bert.wesarg@googlemail.com \
    --cc=avarab@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).