From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: Matthew Hughes <matthewhughes934@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Update documentation/discoverability around `scalar`
Date: Sat, 29 Nov 2025 15:09:52 -0800 [thread overview]
Message-ID: <xmqqqztgcu67.fsf@gitster.g> (raw)
In-Reply-To: <FD92D0BF-E2C0-485E-A121-4C92BD20F7F9@gmail.com> (Ben Knoble's message of "Sat, 29 Nov 2025 14:55:10 -0500")
Ben Knoble <ben.knoble@gmail.com> writes:
>> Le 29 nov. 2025 à 13:33, Matthew Hughes <matthewhughes934@gmail.com> a écrit :
>>
>> A couple of changes following on from a discussion around the
>> discoverability of `scalar` config changes[1].
>>
>> Following that thread, I was additionally working on a patch that would
>> involve commenting each of the changes and why they're set. But that was
>> taking me longer than expected so I figured I get these smaller changes
>> up rather than waiting to complete everything.
>
> I think Stolee implemented a few similar things in GitGitGadget PR 2010
Also known as
https://lore.kernel.org/git/pull.2010.git.1764195516.gitgitgadget@gmail.com/
queued on 'ds/doc-scalar-config' topic that ends at c483f0a5
(scalar: document config settings, 2025-11-26).
next prev parent reply other threads:[~2025-11-29 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-29 18:32 [PATCH v2 0/2] Update documentation/discoverability around `scalar` Matthew Hughes
2025-11-29 18:33 ` [PATCH v2 1/2] scalar: add comments when setting config Matthew Hughes
2025-11-29 18:33 ` [PATCH v2 2/2] config: document `gui.GCWarning` Matthew Hughes
2025-11-29 19:55 ` [PATCH v2 0/2] Update documentation/discoverability around `scalar` Ben Knoble
2025-11-29 23:05 ` Matthew Hughes
2025-11-30 19:54 ` Derrick Stolee
2025-11-29 23:09 ` Junio C Hamano [this message]
2025-11-30 18:39 ` Ben Knoble
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=xmqqqztgcu67.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthewhughes934@gmail.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;
as well as URLs for NNTP newsgroup(s).