From: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
To: git@vger.kernel.org
Cc: jltobler@gmail.com, ps@pks.im,
"Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
Subject: [PATCH v2 0/1] repo: add filtering options to "repo structure"
Date: Mon, 5 Oct 2026 13:40:43 -0400 [thread overview]
Message-ID: <20261005174045.1900391-1-markchucarroll@fastmail.com> (raw)
In-Reply-To: <20260924164503.119506-2-markchucarroll@fastmail.com>
"git repo structure" provides a collection of useful information
about the information stored in a repo. In particular, it's
valuable for diagnosing performance issues caused by large objects
stored in a repo.
The current implementation of "git repo stucture" provides summary
information about everything in the repository - all of the
branches, remotes, tags, stashes, and notes. But sometimes
to properly diagnose a problem, it's useful to be able to
get information about the specific part of the repo that's
exhibiting a problem.
Add the option to specify a set of filters in the form
of a list of include and exclude queries. Each of these
specifies a commit or ref or range. The set of objects processed
will consist of all objects reachable from any of the
includes which are _not_ reached exclusively by paths
including any of the excludes.
Updates since v1: this change has been completely rewritten. The
original version implemented filters the same way as
"git-sizer", by selecting object types to include or exclude.
This version drops he type-based filters in favor of
specifying object traversal roots and exclusions.
Mark C. Chu-Carroll (1):
repo: add filtering options to "repo structure"
Documentation/git-repo.adoc | 41 ++++++++++++++++--
builtin/repo.c | 16 +++++--
t/t1901-repo-structure.sh | 84 +++++++++++++++++++++++++++++++++++++
3 files changed, 133 insertions(+), 8 deletions(-)
--
2.53.0
next prev parent reply other threads:[~2026-10-05 17:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:45 [PATCH 0/1] repo: add filtering options to "repo structure" Mark C. Chu-Carroll
2026-09-24 16:45 ` [PATCH 1/1] " Mark C. Chu-Carroll
2026-09-30 16:28 ` Patrick Steinhardt
2026-10-05 18:52 ` Mark C. Chu-Carroll
2026-10-05 17:40 ` Mark C. Chu-Carroll [this message]
2026-10-05 17:40 ` [PATCH v2 " Mark C. Chu-Carroll
2026-10-06 5:51 ` Patrick Steinhardt
2026-10-08 15:46 ` Kaartic Sivaraam
2026-10-09 15:49 ` Mark C. Chu-Carroll
2026-10-09 18:09 ` [PATCH v3 0/1] repo: add revision " Mark C. Chu-Carroll
2026-10-09 18:09 ` [PATCH v3 1/1] repo: add " Mark C. Chu-Carroll
2026-10-09 21:24 ` Junio C Hamano
2026-10-10 14:31 ` Mark C. Chu-Carroll
2026-10-10 15:05 ` [PATCH v4 0/1] repo: add revision " Mark C. Chu-Carroll
2026-10-10 15:05 ` [PATCH v4 1/1] repo: add " 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=20261005174045.1900391-1-markchucarroll@fastmail.com \
--to=markchucarroll@fastmail.com \
--cc=git@vger.kernel.org \
--cc=jltobler@gmail.com \
--cc=ps@pks.im \
/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