From: Junio C Hamano <gitster@pobox.com>
To: YikunWei <YikunWei@126.com>
Cc: git@vger.kernel.org,
"brian m . carlson" <sandals@crustytoothpaste.net>,
Eric Sunshine <sunshine@sunshineco.com>,
Bruno Haible <bruno@clisp.org>
Subject: Re: [PATCH] doc: include fmt-merge-msg config in the main config doc
Date: Sat, 14 Nov 2026 11:47:45 -0800 [thread overview]
Message-ID: <xmqq33t3p53y.fsf@gitster.g> (raw)
In-Reply-To: <20261113144543.46713-1-YikunWei@126.com> (YikunWei@126.com's message of "Fri, 13 Nov 2026 22:45:42 +0800")
YikunWei <YikunWei@126.com> writes:
> From: Yikun Wei <YikunWei@126.com>
>
> config/fmt-merge-msg.adoc was only included by git-fmt-merge-msg(1),
> so merge.branchdesc, merge.log and merge.suppressDest were missing
> from git-config(1), the central configuration reference. Include it
> in config.adoc (alphabetically between filter and format) so that
> they are listed in `git help config`.
Don't we include merge.adoc which in turn includes this file?
prev parent reply other threads:[~2026-11-14 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 14:45 [PATCH] doc: include fmt-merge-msg config in the main config doc YikunWei
2026-11-14 19:47 ` 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=xmqq33t3p53y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=YikunWei@126.com \
--cc=bruno@clisp.org \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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