Il giorno mar 22 mar 2022 alle ore 07:49 Bagas Sanjaya <bagasdotme@xxxxxxxxx> ha scritto: > > 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. Salutations. You can help me ? I'm having trouble continuing the course and haven't had any answers yet. Or if you can help me figure out who to contact. Thank you for your cooperation. Thank you. But there are many sources that include both of them, the choice would then be arbitrary. However, I follow the various reviews. > -- > An old man doll... just what I always wanted! - Clara
