git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>,
	whydoubt@gmail.com, git@vger.kernel.org,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] blame.c: replace instance of !oidcmp for oideq
Date: Tue, 8 Sep 2020 15:07:34 -0400	[thread overview]
Message-ID: <ce94b41f-e829-d7ca-a5f5-e41748caea81@gmail.com> (raw)
In-Reply-To: <20200907171639.766547-1-eantoranz@gmail.com>

On 9/7/2020 1:16 PM, Edmundo Carmona Antoranz wrote:
> ---

Please include sign-off. I saw you reported your intention there
in another message, but it's probably best to just send it again.

This message could also mention 14438c4 (introduce hasheq() and
oideq(), 2018-08-28) which introduced oideq().

This use of !oidcmp() was introduced by 0906ac2b (blame: use
changed-path Bloom filters, 2020-04-16). My bad. There is no
good reason to introduce this use since it is well after the
oideq() method was introduced.

> @@ -1353,8 +1353,8 @@ static struct blame_origin *find_origin(struct repository *r,
>  	else {
>  		int compute_diff = 1;
>  		if (origin->commit->parents &&
> -		    !oidcmp(&parent->object.oid,
> -			    &origin->commit->parents->item->object.oid))
> +		    oideq(&parent->object.oid,
> +			  &origin->commit->parents->item->object.oid))
>  			compute_diff = maybe_changed_path(r, origin, bd);

The code itself looks correct.

Thanks,
-Stolee

  parent reply	other threads:[~2020-09-08 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07 17:16 [PATCH] blame.c: replace instance of !oidcmp for oideq Edmundo Carmona Antoranz
2020-09-07 17:21 ` Edmundo Carmona Antoranz
2020-09-08 13:55   ` Edmundo Carmona Antoranz
2020-09-08 19:07 ` Derrick Stolee [this message]
2020-09-09  9:11   ` Jeff King
2020-09-09 14:00     ` Edmundo Carmona Antoranz
2020-09-09 17:48       ` Jeff Smith
2020-09-09 19:13       ` Jeff King
2020-09-09 19:17         ` Jeff King
2020-09-09 19:54           ` René Scharfe
2020-09-09 19:58             ` Jeff King
2020-09-09 20:03             ` Junio C Hamano
2020-09-09 20:06           ` Junio C Hamano
2020-09-09 20:43         ` René Scharfe

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=ce94b41f-e829-d7ca-a5f5-e41748caea81@gmail.com \
    --to=stolee@gmail.com \
    --cc=eantoranz@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=whydoubt@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).