git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 3/3] repo: add documentation for level-of-concern.

From
Patrick Steinhardt <ps@pks.im>
Date
Oct 27, 2026, 14:55 UTC
Message-ID
<auC7YzhTbn3q7GPt@pks.im>
In-Reply-To
<20261026-b4-repo-structure-concern-v2-3-e0df34228dc8@fastmail.com>
On Mon, Oct 26, 2026 at 01:43:56PM -0400, Mark C. Chu-Carroll wrote:
Show 16 quoted lines
> ---
>  Documentation/config/repo.adoc | 59 ++++++++++++++++++++++++++++++++++++++++++
>  Documentation/git-repo.adoc    | 27 +++++++++++++++++--
>  2 files changed, 84 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/config/repo.adoc b/Documentation/config/repo.adoc
> new file mode 100644
> index 0000000000..811b099d72
> --- /dev/null
> +++ b/Documentation/config/repo.adoc
> @@ -0,0 +1,59 @@
> +`repo.concern.commit-count`::
> +	Sets the value of the concern threshold for commit count.
> +
> +`repo.concern.tree-count`::
> +	Sets the value of the concern threshold for tree count.

I think this commit can be split and squashed into the other two commits:

  - The change to synopsis and documentation of "--concern" should be
    squashed into the first commit.
  - These config values here should be squashed into the second commit.
Thanks!
Patrick
Previous: Mark C. Chu-CarrollNext: Mark C. Chu-Carroll
Message 11 of 20 in “repo: add degree-of-concern reporting to structure”
  1. 0/3 repo: add degree-of-concern reporting to structureMark C. Chu-Carroll, Oct 21, 2026
  2. 1/3 repo: add level of concern reportingMark C. Chu-Carroll, Oct 21, 2026
  3. 2/3 repo: make concern thresholds configurableMark C. Chu-Carroll, Oct 21, 2026
  4. 3/3 repo: add documentation for level-of-concern.Mark C. Chu-Carroll, Oct 21, 2026
  5. 0/3 repo: add degree-of-concern reporting to structureMark C. Chu-Carroll, Oct 26, 2026
  6. 1/3 repo: add level of concern reportingMark C. Chu-Carroll, Oct 26, 2026
  7. Patrick SteinhardtOct 27, 2026
  8. 2/3 repo: make concern thresholds configurableMark C. Chu-Carroll, Oct 26, 2026
  9. Patrick SteinhardtOct 27, 2026
  10. 3/3 repo: add documentation for level-of-concern.Mark C. Chu-Carroll, Oct 26, 2026
  11. Patrick SteinhardtOct 27, 2026
  12. Mark C. Chu-CarrollOct 28, 2026
  13. 0/2 repo: add degree-of-concern reporting to structureMark C. Chu-Carroll, Oct 27, 2026
  14. 1/2 repo: add level of concern reportingMark C. Chu-Carroll, Oct 27, 2026
  15. 2/2 repo: make concern thresholds configurableMark C. Chu-Carroll, Oct 27, 2026
  16. 0/2 repo: add degree-of-concern reporting to structureMark C. Chu-Carroll, Oct 29, 2026
  17. 1/2 repo: add level of concern reportingMark C. Chu-Carroll, Oct 29, 2026
  18. Junio C HamanoOct 29, 2026
  19. Mark C. Chu-CarrollOct 29, 2026
  20. 2/2 repo: make concern thresholds configurableMark C. Chu-Carroll, Oct 29, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.