From: Junio C Hamano <gitster@pobox.com>
To: "Joel Klinghed" <the_jk@spawned.biz>
Cc: "Joel Klinghed via GitGitGadget" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [PATCH v2] commit: restore --edit when combined with --fixup
Date: Thu, 12 Aug 2021 12:51:18 -0700 [thread overview]
Message-ID: <xmqqbl6230i1.fsf@gitster.g> (raw)
In-Reply-To: <873ec1ab-c062-4306-b3fb-09d32c70cc7f@www.fastmail.com> (Joel Klinghed's message of "Thu, 12 Aug 2021 09:42:06 +0200")
"Joel Klinghed" <the_jk@spawned.biz> writes:
>> Writing this as
>>
>> if (edit_flag < 0)
>>
>> makes it far easier to immediately see that we are talking about a
>> nagetive edit_flag.
>>
>
> Agree, I'll change it.
> I was unsure of the style and copied from the earlier condition:
> if (0 <= edit_flag)
> use_editor = edit_flag;
There are two valid schools of thought when it comes to comparison.
Some folks consider that a comparison between a variable and a
constant is a statement about the variable, hence the expression
should be
if (VARIRABLE comparison-operator CONSTANT)
They will write things like:
if (edit_flag >= 0)
if (edit_flag < 0)
Other folks consider that textual order of the comparison should
match the actual order of the things being compared, as if they are
arranged on a number line, hence the expression should be
if (SMALLER < LARGER)
no matter which one is variable and which one is constant.
They will write:
if (0 <= edit_flag)
if (edit_flag < 0)
The case in question, asserting that edit_flag is negative, is what
both camps agree how to write.
next prev parent reply other threads:[~2021-08-12 19:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 13:49 [PATCH] commit: restore --edit when combined with --fixup Joel Klinghed via GitGitGadget
2021-08-11 20:24 ` Jeff King
2021-08-11 22:10 ` Joel Klinghed
2021-08-11 22:22 ` Jeff King
2021-08-11 23:27 ` brian m. carlson
2021-08-11 23:43 ` [PATCH v2] " Joel Klinghed via GitGitGadget
2021-08-12 5:21 ` Junio C Hamano
2021-08-12 7:42 ` Joel Klinghed
2021-08-12 19:51 ` Junio C Hamano [this message]
2021-08-12 8:02 ` [PATCH v3] " Joel Klinghed via GitGitGadget
2021-08-12 9:32 ` Phillip Wood
2021-08-12 10:01 ` Joel Klinghed
2021-08-13 13:06 ` Phillip Wood
2021-08-13 15:35 ` Joel Klinghed
2021-08-14 15:20 ` Phillip Wood
2021-08-14 21:19 ` Joel Klinghed
2021-08-12 11:55 ` [PATCH v4] " Joel Klinghed via GitGitGadget
2021-08-14 21:40 ` [PATCH v5] " Joel Klinghed via GitGitGadget
2021-08-17 10:06 ` Phillip Wood
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=xmqqbl6230i1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=the_jk@spawned.biz \
/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).