From: Junio C Hamano <gitster@pobox.com>
To: "Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH 1/1] sequencer: fix empty commit check when amending
Date: Fri, 22 Nov 2019 15:52:34 +0900 [thread overview]
Message-ID: <xmqqblt44d3h.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <7d34c0ff805b8637b23d0ef0045370dfc931a3af.1574345181.git.gitgitgadget@gmail.com> (Phillip Wood via GitGitGadget's message of "Thu, 21 Nov 2019 14:06:21 +0000")
"Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com> writes:
> + if (!(flags & ALLOW_EMPTY)) {
> + struct commit *first_parent = current_head;
I would have used first_parent_tree variable instead here. That
way, you did not have to have an overlong ternary expression down
there, I expect.
> + if (flags & AMEND_MSG) {
> + if (current_head->parents) {
> + first_parent = current_head->parents->item;
> + if (repo_parse_commit(r, first_parent)) {
> + res = error(_("could not parse HEAD commit"));
> + goto out;
> + }
> + } else {
> + first_parent = NULL;
> + }
> + }
> + if (oideq(first_parent ? get_commit_tree_oid(first_parent) :
> + the_hash_algo->empty_tree, &tree)) {
Style. It often makes the code much easier to read when you strive
to break lines at the boundary of larger syntactic units. In this
(A ? B : C, D) parameter list, ternary A ? B : C binds much tighter
than the comma after it, so if you are breaking line inside it, you
should break line after the comma, too, i.e.
oideq(first_parent
? get_commit_tree_oid(first_parent)
: the_hash_algo->empty_tree,
&tree)
to avoid appearing if C and D have closer relationship than B and C,
which your version gives.
But I hope that it becomes a moot point, if we computed first_parent_tree
inside the new "if (flags & AMEND_MSG)" block to leave this oideq()
just
if (oideq(first_parent_tree, &tree)) {
next prev parent reply other threads:[~2019-11-22 6:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 14:06 [PATCH 0/1] sequencer: fix empty commit check when amending Phillip Wood via GitGitGadget
2019-11-21 14:06 ` [PATCH 1/1] " Phillip Wood via GitGitGadget
2019-11-22 6:40 ` Junio C Hamano
2019-11-22 11:01 ` Phillip Wood
2019-11-22 6:52 ` Junio C Hamano [this message]
2019-11-22 11:09 ` Phillip Wood
2019-11-22 19:43 ` [PATCH v2 0/1] " Phillip Wood via GitGitGadget
2019-11-22 19:43 ` [PATCH v2 1/1] " Phillip Wood via GitGitGadget
2019-11-23 2:02 ` Junio C Hamano
2019-11-23 2:03 ` Junio C Hamano
2019-11-23 9:54 ` Phillip Wood
2019-11-24 10:52 ` Phillip Wood
2019-11-25 3:00 ` Junio C Hamano
2019-11-25 14:23 ` Phillip Wood
2019-11-25 15:53 ` Johannes Schindelin
2019-11-25 16:10 ` Eric Sunshine
2019-11-25 22:52 ` Johannes Schindelin
2019-11-25 16:42 ` Phillip Wood
2019-11-26 1:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqblt44d3h.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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).