All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark C. Chu-Carroll" <markchucarroll@fastmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 3/3] repo: add documentation for level-of-concern.
Date: Wed, 28 Oct 2026 09:23:38 -0400	[thread overview]
Message-ID: <637732be5efcc579fa737004ca4132bc@fastmail.com> (raw)
In-Reply-To: <auC7YzhTbn3q7GPt@pks.im>


On Tue, 27 Oct 2026 15:55:31 +0100, Patrick Steinhardt <ps@pks.im> wrote:
> On Mon, Oct 26, 2026 at 01:43:56PM -0400, Mark C. Chu-Carroll wrote:
> > ---
> >  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.


Yeah, that makes sense. 
(Note, this will appear out of order; original send failed yesterday.)

       -Mark

  reply	other threads:[~2026-10-28 13:23 UTC|newest]

Thread overview: 20+ 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 [this message]
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

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=637732be5efcc579fa737004ca4132bc@fastmail.com \
    --to=markchucarroll@fastmail.com \
    --cc=git@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.