From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Michael Haggerty <mhagger@alum.mit.edu>,
Kevin Willford <kewillf@microsoft.com>,
Xiaolong Ye <xiaolong.ye@intel.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: [PATCH v3 0/2] patch-id for merges
Date: Mon, 12 Sep 2016 10:18:33 -0700 [thread overview]
Message-ID: <xmqq37l53ul2.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160912155930.2acw4265nfjq3uyj@sigill.intra.peff.net> (Jeff King's message of "Mon, 12 Sep 2016 11:59:31 -0400")
Jeff King <peff@peff.net> writes:
> That looks like the patch below (as a replacement for patch 2), which is
> even less invasive. It also performs a little better on my example case,
> because we avoid adding merges to the hashmap entirely.
After reading it, I did not find [v3 2/2] is too bad either, but
this is even better ;-)
> diff --git a/patch-ids.c b/patch-ids.c
> index 77e4663..5d2d96a 100644
> --- a/patch-ids.c
> +++ b/patch-ids.c
> @@ -7,10 +7,12 @@
> int commit_patch_id(struct commit *commit, struct diff_options *options,
> unsigned char *sha1, int diff_header_only)
> {
> - if (commit->parents)
> + if (commit->parents) {
> + if (commit->parents->next)
> + return -1;
> diff_tree_sha1(commit->parents->item->object.oid.hash,
> commit->object.oid.hash, "", options);
> - else
> + } else
> diff_root_tree_sha1(commit->object.oid.hash, "", options);
This looks familiar ;-)
> @@ -72,11 +74,20 @@ static int init_patch_id_entry(struct patch_id *patch,
> return 0;
> }
>
> +static int patch_id_defined(struct commit *commit)
> +{
> + /* must be 0 or 1 parents */
> + return !commit->parents || !commit->parents->next;
> +}
If we make the first hunk begin like so:
> + if (commit->parents) {
> + if (!patch_id_defined(commit))
> + return -1;
I wonder if the compiler gives us the same code.
> struct patch_id *has_commit_patch_id(struct commit *commit,
> struct patch_ids *ids)
> {
> struct patch_id patch;
>
> + if (!patch_id_defined(commit))
> + return NULL;
> +
> memset(&patch, 0, sizeof(patch));
> if (init_patch_id_entry(&patch, commit, ids))
> return NULL;
> @@ -89,6 +100,9 @@ struct patch_id *add_commit_patch_id(struct commit *commit,
> {
> struct patch_id *key = xcalloc(1, sizeof(*key));
>
> + if (!patch_id_defined(commit))
> + return NULL;
> +
> if (init_patch_id_entry(key, commit, ids)) {
> free(key);
> return NULL;
Yup, these two hunks look a lot nicer.
> I'd probably do a preparatory patch to drop the return value from
> add_commit_patch_id(). No callers actually look at it.
Thanks.
next prev parent reply other threads:[~2016-09-12 17:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:53 [RFC/PATCH 0/2] more patch-id speedups Jeff King
2016-09-07 7:54 ` [PATCH 1/2] patch-ids: turn off rename detection Jeff King
2016-09-07 12:53 ` Johannes Schindelin
2016-09-07 7:54 ` [PATCH 2/2] patch-ids: skip merge commits Jeff King
2016-09-07 12:52 ` Johannes Schindelin
2016-09-07 18:46 ` Jeff King
2016-09-07 22:08 ` Jeff King
2016-09-07 13:06 ` [RFC/PATCH 0/2] more patch-id speedups Johannes Schindelin
2016-09-07 18:49 ` Jeff King
2016-09-07 22:01 ` [RFC/PATCH v2 0/3] patch-id for merges Jeff King
2016-09-07 22:02 ` [PATCH 1/3] patch-ids: turn off rename detection Jeff King
2016-09-07 22:12 ` Jacob Keller
2016-09-07 22:04 ` [PATCH 2/3] diff_flush_patch_id: stop returning error result Jeff King
2016-09-08 0:51 ` Ramsay Jones
2016-09-08 7:20 ` Jeff King
2016-09-09 10:28 ` Johannes Schindelin
2016-09-09 10:40 ` Jeff King
2016-09-09 12:58 ` Johannes Schindelin
2016-09-09 19:37 ` Jeff King
2016-09-07 22:04 ` [PATCH 3/3] patch-ids: use commit sha1 as patch-id for merge commits Jeff King
2016-09-07 22:28 ` Jacob Keller
2016-09-07 22:38 ` Jeff King
2016-09-07 22:51 ` [RFC/PATCH v2 0/3] patch-id for merges Josh Triplett
2016-09-08 7:30 ` Jeff King
2016-09-09 20:34 ` [PATCH v3 0/2] " Jeff King
2016-09-09 20:34 ` [PATCH v3 1/2] patch-ids: turn off rename detection Jeff King
2016-09-09 20:34 ` [PATCH v3 2/2] patch-ids: define patch-id of merge commits as "null" Jeff King
2016-09-09 20:37 ` Jeff King
2016-09-09 21:13 ` Junio C Hamano
2016-09-09 21:01 ` [PATCH v3 0/2] patch-id for merges Junio C Hamano
2016-09-12 15:59 ` Jeff King
2016-09-12 17:18 ` Junio C Hamano [this message]
2016-09-12 17:56 ` Jeff King
2016-09-12 20:44 ` Junio C Hamano
2016-09-25 18:25 ` Johannes Schindelin
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=xmqq37l53ul2.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=josh@joshtriplett.org \
--cc=kewillf@microsoft.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
--cc=xiaolong.ye@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.