From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 2/2] merge/pull: extend merge.stat configuration variable to cover --compact-summary
Date: Fri, 13 Jun 2025 09:38:30 -0700 [thread overview]
Message-ID: <xmqqv7oz8um1.fsf@gitster.g> (raw)
In-Reply-To: <deb4951a-5d1b-416d-bcad-5d675d8155cc@app.fastmail.com> (Kristoffer Haugsbakk's message of "Fri, 13 Jun 2025 14:09:52 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Fri, Jun 13, 2025, at 00:25, Junio C Hamano wrote:
>> Extend it to be "Boolean or text", that takes false, true, or
>> "compact", with the last one triggering the --compact-summary
>> option introduced earlier.
>
> Would it make sense to make `diffstat` an alias for `true`? I’m not
> sure since you need to keep `true` anyway so you still have that
> historical artifact (?)[1] of `true` meaning `diffstat`.
Correct. But people can bikeshed about adding such synonyms later
without breaking existing users, so I would not consider such a
tweak for the initial version.
> There’s also several places in this doc which uses something similar
> judging by a search for “defaults to”. Only exception is
> `merge.renameLimit`:
>
> If not specified, defaults to
Having something before "Defaults to X" (like "if left unspecified"
etc.) may not be logically and technically needed, as that is the
definion of what the "default" is.
Having said that, I somehow find the resulting sentence easier to
read with such an introducer, but perhaps it is just me.
Among the output of
$ git grep -E -i ', default' Documentation/
we already have quite a few of them.
Thanks.
Documentation/config/commitgraph.adoc:repository, defaulting to 1 if there are none.
Documentation/config/merge.adoc: rename detection during a merge. If not specified, defaults
Documentation/fetch-options.adoc:is set (see linkgit:git-config[1]), defaulting to 'on-demand' if unset.
Documentation/git-init.adoc:The option can have the following values, defaulting to `group` if no value
Documentation/git-send-email.adoc:value; if that is unspecified, default to `auto`.
Documentation/git-send-email.adoc: value; if that is unspecified, default to --signed-off-by-cc.
Documentation/git-send-email.adoc: configuration value; if that is unspecified, default to --no-cc-cover.
Documentation/git-send-email.adoc: configuration value; if that is unspecified, default to --no-to-cover.
Documentation/git-send-email.adoc:that is unspecified, default to 'self' if --suppress-from is
Documentation/git-send-email.adoc: value; if that is unspecified, default to --no-suppress-from.
Documentation/git-send-email.adoc:is unspecified, default to 'auto' unless any of the suppress options
prev parent reply other threads:[~2025-06-13 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 22:25 [PATCH v2 0/2] git pull/merge --compact-summary Junio C Hamano
2025-06-12 22:25 ` [PATCH v2 1/2] merge/pull: --compact-summary Junio C Hamano
2025-06-13 12:07 ` Kristoffer Haugsbakk
2025-06-13 16:26 ` Junio C Hamano
2025-06-12 22:25 ` [PATCH v2 2/2] merge/pull: extend merge.stat configuration variable to cover --compact-summary Junio C Hamano
2025-06-13 12:09 ` Kristoffer Haugsbakk
2025-06-13 16:38 ` Junio C Hamano [this message]
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=xmqqv7oz8um1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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