From: Junio C Hamano <gitster@pobox.com>
To: "dsal3389 via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, dsal3389 <dsal3389@gmail.com>
Subject: Re: [PATCH 0/2] Minor Refactors: remove useless else
Date: Thu, 06 Oct 2022 10:06:43 -0700 [thread overview]
Message-ID: <xmqqmta8lw4c.fsf@gitster.g> (raw)
In-Reply-To: pull.1355.git.git.1665056747.gitgitgadget@gmail.com
"dsal3389 via GitGitGadget" <gitgitgadget@gmail.com> writes:
> git.c removed redundant else statement - it is redundant because all we
> actually need is to check if there are no arguments, the program print
> helpful information to the screen and exit, we don't need the else for that
>
> git-p4.py L371 - remove redundant else statement - same as git.c (made sure
> not to repeat what was already done on #1349
> [https://github.com/git/git/pull/1349]) git-p4.py L404 - minor, there is no
> need to decode the output and iterate over the variable if we may exit
>
> dsal3389 (2):
> python file more pytonic, adjust "if" and "for"
> removed else statement
>
> git-p4.py | 9 ++++-----
> git.c | 14 ++++++++------
> 2 files changed, 12 insertions(+), 11 deletions(-)
Welcome to the Git development community.
A few general suggestions.
* Familiarlize yourself with Documentation/CodingGuidelines and
Documentation/SubmittingPatches.
* See how commits in the project are explained in their log
messages in "git shortlog --no-merges -n100" (for how their
titles are written to help distinguish them among many other
commits) and "git log --no-merges -n100" (for how they explain
why making their changes is a good idea and helps the project).
* Make sure the name and the e-mail used as the author of your
commits match the name and the e-mail on the Signed-off-by: line
in them.
* Spell check before sending things out to the public list.
next prev parent reply other threads:[~2022-10-06 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 11:45 [PATCH 0/2] Minor Refactors: remove useless else dsal3389 via GitGitGadget
2022-10-06 11:45 ` [PATCH 1/2] python file more pytonic, adjust "if" and "for" dsal3389 via GitGitGadget
2022-10-06 16:02 ` Victoria Dye
2022-10-06 17:16 ` Junio C Hamano
2022-10-06 11:45 ` [PATCH 2/2] removed else statement dsal3389 via GitGitGadget
2022-10-06 16:14 ` Victoria Dye
2022-10-07 18:35 ` Junio C Hamano
2022-10-06 17:16 ` Junio C Hamano
2022-10-06 17:06 ` Junio C Hamano [this message]
2022-10-07 14:38 ` [PATCH v2 0/2] git.c: improve readability | git-p4: minor optimization Daniel Sonbolian via GitGitGadget
2022-10-07 14:38 ` [PATCH v2 1/2] git-p4: minor optimization in read_pip_lines Daniel Sonbolian via GitGitGadget
2022-10-07 15:17 ` Phillip Wood
2022-10-07 17:28 ` Junio C Hamano
2022-10-07 14:38 ` [PATCH v2 2/2] git.c: improve code readability in cmd_main Daniel Sonbolian via GitGitGadget
2022-10-08 16:21 ` [PATCH v3] " Daniel Sonbolian via GitGitGadget
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqmta8lw4c.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsal3389@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.
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 NNTP newsgroup(s).