From: Junio C Hamano <gitster@pobox.com>
To: "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, peff@peff.net, me@ttaylorr.com,
szeder.dev@gmail.com, Derrick Stolee <dstolee@microsoft.com>
Subject: Re: [PATCH 1/1] fetch: set size_multiple in split_commit_graph_opts
Date: Thu, 02 Jan 2020 13:49:58 -0800 [thread overview]
Message-ID: <xmqq7e29edfd.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <91d89356a20625d04af74d458c28b32445e760c1.1577981654.git.gitgitgadget@gmail.com> (Derrick Stolee via GitGitGadget's message of "Thu, 02 Jan 2020 16:14:14 +0000")
"Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> This problem is due to two failures:
>
> 1. It is unclear that we can add the flag COMMIT_GRAPH_WRITE_SPLIT
> with a NULL split_opts.
> 2. If we have a non-NULL split_opts, then we override the default
> values even if a zero value is given.
>
> Correct both of these issues. First, do not override size_mult when
> the options provide a zero value. Second, stop creating a split_opts
> in the fetch builtin.
OK, so there is the hardcoded default 2 in the code, and split_opts
structure *can* override it, but 0 in the field of the structure is
meant to signal "no, I do not have any value to override the
default", not "I do want to set the multiple to 0"?
Makes sense. Will queue.
Thanks.
> Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
> ---
> builtin/fetch.c | 4 +---
> commit-graph.c | 4 +++-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> index f8765b385b..b4c6d921d0 100644
> --- a/builtin/fetch.c
> +++ b/builtin/fetch.c
> @@ -1866,15 +1866,13 @@ int cmd_fetch(int argc, const char **argv, const char *prefix)
> (fetch_write_commit_graph < 0 &&
> the_repository->settings.fetch_write_commit_graph)) {
> int commit_graph_flags = COMMIT_GRAPH_WRITE_SPLIT;
> - struct split_commit_graph_opts split_opts;
> - memset(&split_opts, 0, sizeof(struct split_commit_graph_opts));
>
> if (progress)
> commit_graph_flags |= COMMIT_GRAPH_WRITE_PROGRESS;
>
> write_commit_graph_reachable(get_object_directory(),
> commit_graph_flags,
> - &split_opts);
> + NULL);
> }
>
> close_object_store(the_repository->objects);
> diff --git a/commit-graph.c b/commit-graph.c
> index e771394aff..b205e65ed1 100644
> --- a/commit-graph.c
> +++ b/commit-graph.c
> @@ -1542,7 +1542,9 @@ static void split_graph_merge_strategy(struct write_commit_graph_context *ctx)
>
> if (ctx->split_opts) {
> max_commits = ctx->split_opts->max_commits;
> - size_mult = ctx->split_opts->size_multiple;
> +
> + if (ctx->split_opts->size_multiple)
> + size_mult = ctx->split_opts->size_multiple;
> }
>
> g = ctx->r->objects->commit_graph;
next prev parent reply other threads:[~2020-01-02 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 16:14 [PATCH 0/1] [PERF BUG] Fix size_mult option in fetch.writeCommitGraph Derrick Stolee via GitGitGadget
2020-01-02 16:14 ` [PATCH 1/1] fetch: set size_multiple in split_commit_graph_opts Derrick Stolee via GitGitGadget
2020-01-02 16:20 ` Derrick Stolee
2020-01-02 21:49 ` Junio C Hamano [this message]
2020-01-03 13:07 ` Derrick Stolee
2020-01-06 19:39 ` Jeff King
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=xmqq7e29edfd.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=me@ttaylorr.com \
--cc=peff@peff.net \
--cc=szeder.dev@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).