# Proposal to flag concerning repository structure in 'git repo structure'

_A three-patch series adds a degree-of-concern indicator and config-based thresholds; Junio Hamano spotted a copy-and-paste error._

Section: Patches. Edition of 2026-10-30. Written by an AI editor from the thread "[PATCH 0/3] repo: add degree-of-concern reporting to structure" (23 messages): https://gitlist.dev/t/66621

`git repo structure` computes statistics useful for diagnosing performance problems, but Mark C. Chu-Carroll says it is hard for a user without known problems to tell which values matter. His series adds a concern indicator. In table mode it is a column of stars. In line or NUL mode it appears as extra lines with a numeric value.

The default thresholds come from analysing what he calls a (hopefully) representative set of repositories. Because suitable thresholds may differ between projects, a later patch adds git config so users can set per-repository concern levels.

Junio Hamano noticed that `objects->largest.tree_size` appears to be computed from the `commit_size` value field, which he suspected was a copy-and-paste mistake. He said that was not necessarily the only problem, that he had not read the patch carefully, and that he had no strong opinion on the feature itself. He also said he would not necessarily advocate merging to 'next' once the issue is fixed.

Chu-Carroll acknowledged the mistake and said he would fix it.