From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Elia Pinto <gitter.spiros@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 00/41] use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
Date: Tue, 22 Mar 2022 13:49:24 +0700 [thread overview]
Message-ID: <5dea325c-c80c-c203-c42e-b55e58b717de@gmail.com> (raw)
In-Reply-To: <20220321225523.724509-1-gitter.spiros@gmail.com>
On 22/03/22 05.54, Elia Pinto wrote:
> Elia Pinto (41):
> archive.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> branch.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> am.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> blame.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> commit.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> credential-cache--daemon.c: use the stdlib EXIT_SUCCESS or
> EXIT_FAILURE exit status
> help.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> init-db.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> mailsplit.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> merge-index.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> merge.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> pull.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> rebase.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> remote-ext.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> rev-parse.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> rm.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> shortlog.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> show-branch.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> stash.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> tag.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> unpack-objects.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit
> status
> update-index.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit
> status
> obstack.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> git-credential-osxkeychain.c: use the stdlib EXIT_SUCCESS or
> EXIT_FAILURE exit status
> git-credential-wincred.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE
> exit status
> daemon.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> git.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> help.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> http-backend.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit
> status
> parse-options.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit
> status
> path.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> remote-curl.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> run-command.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> setup.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> shell.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> test-json-writer.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit
> status
> test-reach.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> test-submodule-config.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE
> exit status
> test-submodule-nested-repo-config.c: use the stdlib EXIT_SUCCESS or
> EXIT_FAILURE exit status
> upload-pack.c: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
> exit.cocci: use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status
>
I think we should only have 2 patches in this series: the first is to replace
with EXIT_SUCCESS, and second is to replace with EXIT_FAILURE.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-03-22 6:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 22:54 [PATCH 00/41] use the stdlib EXIT_SUCCESS or EXIT_FAILURE exit status Elia Pinto
2022-03-21 22:54 ` [PATCH 01/41] archive.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 02/41] branch.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 03/41] am.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 04/41] blame.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 05/41] commit.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 06/41] credential-cache--daemon.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 07/41] help.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 08/41] init-db.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 09/41] mailsplit.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 10/41] merge-index.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 11/41] merge.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 12/41] pull.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 13/41] rebase.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 14/41] remote-ext.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 15/41] rev-parse.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 16/41] rm.c: " Elia Pinto
2022-03-21 22:54 ` [PATCH 17/41] shortlog.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 18/41] show-branch.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 19/41] stash.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 20/41] tag.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 21/41] unpack-objects.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 22/41] update-index.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 23/41] obstack.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 24/41] git-credential-osxkeychain.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 25/41] git-credential-wincred.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 26/41] daemon.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 27/41] git.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 28/41] help.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 29/41] http-backend.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 30/41] parse-options.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 31/41] path.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 32/41] remote-curl.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 33/41] run-command.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 34/41] setup.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 35/41] shell.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 36/41] test-json-writer.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 37/41] test-reach.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 38/41] test-submodule-config.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 39/41] test-submodule-nested-repo-config.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 40/41] upload-pack.c: " Elia Pinto
2022-03-21 22:55 ` [PATCH 41/41] exit.cocci: " Elia Pinto
2022-03-22 6:49 ` Bagas Sanjaya [this message]
2022-03-22 8:45 ` [PATCH 00/41] " Elia Pinto
2022-03-22 11:21 ` Bagas Sanjaya
2022-03-22 8:26 ` Ævar Arnfjörð Bjarmason
2022-03-22 17:47 ` Elia Pinto
2022-03-23 11:13 ` Junio C Hamano
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=5dea325c-c80c-c203-c42e-b55e58b717de@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitter.spiros@gmail.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.
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).