From: Patrick Steinhardt <ps@pks.im>
To: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/3] repo: make concern thresholds configurable
Date: Tue, 27 Oct 2026 15:55:25 +0100 [thread overview]
Message-ID: <auC7XTg6YXl6xAM3@pks.im> (raw)
In-Reply-To: <20261026-b4-repo-structure-concern-v2-2-e0df34228dc8@fastmail.com>
On Mon, Oct 26, 2026 at 01:43:55PM -0400, Mark C. Chu-Carroll wrote:
> diff --git a/builtin/repo.c b/builtin/repo.c
> index a450497d4e..ed579e6685 100644
> --- a/builtin/repo.c
> +++ b/builtin/repo.c
> @@ -386,40 +389,43 @@ enum concern_stat {
> CONCERN_STAT_TREE_INFLATED_SIZE,
> CONCERN_STAT_BLOB_INFLATED_SIZE,
> CONCERN_STAT_TAG_INFLATED_SIZE,
> + CONCERN_STAT_MAXIMUM
> };
>
> -struct concern_stat_threshold repo_structure_concern_thresholds[] = {
> - { .name = "commit_count", .threshold = 19 },
> - {.name = "tree_count", .threshold = 21 },
> - { .name = "blob_count", .threshold = 22 },
> - { .name = "tag_count", .threshold = 15 },
> - { .name = "commit_size", .threshold = 28 },
> - { .name = "tree_size", .threshold = 27 },
> - { .name = "blob_size", .threshold = 36 },
> - { .name = "tags_size", .threshold = 18 },
> - { .name = "commit_largest", .threshold = 18 },
> - { .name = "tree_largest", .threshold = 18 },
> - { .name = "blob_largest", .threshold = 26 },
> - { .name = "tag_largest", .threshold = 15 },
> - { .name = "commit_inflated_size", .threshold = 28 },
> - { .name = "tree_inflated_size", .threshold = 32 },
> - { .name = "blob_inflated_size", .threshold = 34 },
> - { .name = "tag_inflated_size", .threshold = 25}
> +struct concern_stat_threshold concern_stat_thresholds[] = {
> + { .name = "commit-count", .threshold = 19 },
> + { .name = "tree-count", .threshold = 21 },
> + { .name = "blob-count", .threshold = 22 },
> + { .name = "tag-count", .threshold = 15 },
> + { .name = "commit-size", .threshold = 28 },
> + { .name = "tree-size", .threshold = 27 },
> + { .name = "blob-size", .threshold = 36 },
> + { .name = "tag-size", .threshold = 18 },
> + { .name = "commit-largest", .threshold = 18 },
> + { .name = "tree-largest", .threshold = 18 },
> + { .name = "blob-largest", .threshold = 26 },
> + { .name = "tag-largest", .threshold = 15 },
> + { .name = "commit-inflated-size", .threshold = 28 },
> + { .name = "tree-inflated-size", .threshold = 32 },
> + { .name = "blob-inflated-size", .threshold = 34 },
> + { .name = "tag-inflated-size", .threshold = 25},
> + { 0 }
> };
This commit seems to fix up a couple of issues introduced in the
preceding commit. We generally require that every patch of a patch
series should compile and pass all tests so that we can bisect our
history.
Patrick
next prev parent reply other threads:[~2026-10-27 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 13:55 [PATCH 0/3] repo: add degree-of-concern reporting to structure Mark C. Chu-Carroll
2026-10-21 13:55 ` [PATCH 1/3] repo: add level of concern reporting Mark C. Chu-Carroll
2026-10-21 13:55 ` [PATCH 2/3] repo: make concern thresholds configurable Mark C. Chu-Carroll
2026-10-21 13:55 ` [PATCH 3/3] repo: add documentation for level-of-concern Mark C. Chu-Carroll
2026-10-26 17:43 ` [PATCH v2 0/3] repo: add degree-of-concern reporting to structure Mark C. Chu-Carroll
2026-10-26 17:43 ` [PATCH v2 1/3] repo: add level of concern reporting Mark C. Chu-Carroll
2026-10-27 14:55 ` Patrick Steinhardt
2026-10-26 17:43 ` [PATCH v2 2/3] repo: make concern thresholds configurable Mark C. Chu-Carroll
2026-10-27 14:55 ` Patrick Steinhardt [this message]
2026-10-26 17:43 ` [PATCH v2 3/3] repo: add documentation for level-of-concern Mark C. Chu-Carroll
2026-10-27 14:55 ` Patrick Steinhardt
2026-10-28 13:23 ` Mark C. Chu-Carroll
2026-10-27 15:39 ` [PATCH v3 0/2] repo: add degree-of-concern reporting to structure Mark C. Chu-Carroll
2026-10-27 15:39 ` [PATCH v3 1/2] repo: add level of concern reporting Mark C. Chu-Carroll
2026-10-27 15:39 ` [PATCH v3 2/2] repo: make concern thresholds configurable Mark C. Chu-Carroll
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=auC7XTg6YXl6xAM3@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=markchucarroll@fastmail.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