From: Junio C Hamano <gitster@pobox.com>
To: "Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"Jean-Noël Avila" <jn.avila@free.fr>
Subject: Re: [PATCH v2 4/5] doc: convert git commit config to new format
Date: Wed, 15 Jan 2025 15:49:27 -0800 [thread overview]
Message-ID: <xmqqbjw7vdrs.fsf@gitster.g> (raw)
In-Reply-To: <9216554bd7096f2543e987fc7fd20f5e64630187.1736972628.git.gitgitgadget@gmail.com> ("Jean-Noël Avila via GitGitGadget"'s message of "Wed, 15 Jan 2025 20:23:47 +0000")
"Jean-Noël Avila via GitGitGadget" <gitgitgadget@gmail.com> writes:
> +ifdef::git-commit[]
> +:see-git-commit:
> +endif::git-commit[]
> +ifndef::git-commit[]
> +:see-git-commit: See linkgit:git-commit[1] for details.
> +endif::git-commit[]
> +`commit.cleanup`::
> This setting overrides the default of the `--cleanup` option in
> - `git commit`. See linkgit:git-commit[1] for details. Changing the
> - default can be useful when you always want to keep lines that begin
> + `git commit`. {see-git-commit} Changing the default can be useful
> + when you always want to keep lines that begin
OK.
next prev parent reply other threads:[~2025-01-15 23:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 13:47 [PATCH 0/3] Doc git commit Jean-Noël Avila via GitGitGadget
2025-01-03 13:47 ` [PATCH 1/3] doc: git-commit: apply new documentation guidelines Jean-Noël Avila via GitGitGadget
2025-01-06 7:38 ` Patrick Steinhardt
2025-01-07 21:14 ` Jean-Noël AVILA
2025-01-03 13:47 ` [PATCH 2/3] doc: git-commit.txt: convert git commit config to new format Jean-Noël Avila via GitGitGadget
2025-01-03 13:47 ` [PATCH 3/3] doc: git-commit: migrate secondary files " Jean-Noël Avila via GitGitGadget
2025-01-15 20:23 ` [PATCH v2 0/5] Doc git commit Jean-Noël Avila via GitGitGadget
2025-01-15 20:23 ` [PATCH v2 1/5] doc: apply new documentation guidelines to " Jean-Noël Avila via GitGitGadget
2025-01-15 23:46 ` Junio C Hamano
2025-01-15 20:23 ` [PATCH v2 2/5] doc: the mode param of -u of git commit is optional Jean-Noël Avila via GitGitGadget
2025-01-15 20:23 ` [PATCH v2 3/5] doc: make more direct explanations in git commit options Jean-Noël Avila via GitGitGadget
2025-01-15 20:23 ` [PATCH v2 4/5] doc: convert git commit config to new format Jean-Noël Avila via GitGitGadget
2025-01-15 23:49 ` Junio C Hamano [this message]
2025-01-15 20:23 ` [PATCH v2 5/5] doc: migrate git-commit manpage secondary files " Jean-Noël Avila via GitGitGadget
2025-01-16 10:17 ` Patrick Steinhardt
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=xmqqbjw7vdrs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=jn.avila@free.fr \
--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 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).