Re: [PATCH] remote: add meaningful exit code on missing/existing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Oct 26, 2020 at 3:48 PM Ævar Arnfjörð Bjarmason
<avarab@xxxxxxxxx> 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
>  --------
>




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux