From: Junio C Hamano <gitster@pobox.com>
To: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v5 1/2] repo: add level of concern reporting
Date: Thu, 19 Nov 2026 11:44:43 -0800 [thread overview]
Message-ID: <xmqqwlq8wqqc.fsf@gitster.g> (raw)
In-Reply-To: <20261102-b4-repo-structure-concern-v5-1-2d8f37b70b75@fastmail.com> (Mark C. Chu-Carroll's message of "Mon, 02 Nov 2026 11:32:43 -0500")
"Mark C. Chu-Carroll" <markchucarroll@fastmail.com> writes:
> "git repo structure" computes a set of statistics
> that are useful for diagnosing performance issues in
> a git repository.
By the way, I find it very troublesome for this feature to squat on
the name "structure", as what *this* "structure" gives the users is
not about the structure of the repository at all. You are giving
various stats on objects found in the repository and nothing else.
From the name "structure", I would expect that we can learn various
things such as:
* How wide or deep are the trees the contents are being tracked in?
* How many branches are active in the repository? How do these
branches get integrated? Into a single 'trunk'? With many
maintenance tracks? How many?
* How are the names of these branches structured? By topic? By
contributor names? Something else?
in addition to counts and weights of various object types.
And more importantly, we should be able to compare these structural
characteristics across various repositories and projects.
Hopefully it is not too late, as "git repo" as a whole is still
marked as experimental. Once some of the subfeatures in the command
prove useful, hopefully they will be given a more appropriate name
and UI and migrate out of the experimental "git repo" umbrella.
next prev parent reply other threads:[~2026-11-19 19:44 UTC|newest]
Thread overview: 26+ 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
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
2026-10-29 17:52 ` [PATCH v4 0/2] repo: add degree-of-concern reporting to structure Mark C. Chu-Carroll
2026-10-29 17:52 ` [PATCH v4 1/2] repo: add level of concern reporting Mark C. Chu-Carroll
2026-10-29 19:53 ` Junio C Hamano
2026-10-29 20:20 ` Mark C. Chu-Carroll
2026-10-29 17:52 ` [PATCH v4 2/2] repo: make concern thresholds configurable Mark C. Chu-Carroll
2026-11-02 16:32 ` [PATCH v5 0/2] repo: add degree-of-concern reporting to structure Mark C. Chu-Carroll
2026-11-02 16:32 ` [PATCH v5 1/2] repo: add level of concern reporting Mark C. Chu-Carroll
2026-11-18 17:34 ` Christian Couder
2026-11-19 19:44 ` Junio C Hamano [this message]
2026-11-02 16:32 ` [PATCH v5 2/2] repo: make concern thresholds configurable Mark C. Chu-Carroll
2026-11-18 17:36 ` Christian Couder
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=xmqqwlq8wqqc.fsf@gitster.g \
--to=gitster@pobox.com \
--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