From: Junio C Hamano <gitster@pobox.com>
To: Sergey Organov <sorganov@gmail.com>
Cc: git@vger.kernel.org, John Cai <johncai86@gmail.com>
Subject: Re: [PATCH 1/1] doc/diff-options: fix link to generating patch section
Date: Tue, 05 Sep 2023 15:49:04 -0700 [thread overview]
Message-ID: <xmqq34zsqlr3.fsf@gitster.g> (raw)
In-Reply-To: <87zg20qzhg.fsf@osv.gnss.ru> (Sergey Organov's message of "Tue, 05 Sep 2023 20:52:27 +0300")
Sergey Organov <sorganov@gmail.com> writes:
> First, there is no need for conditional referencing, as all the files
> that include "diff-options.txt" eventually include
> "diff-generate-patch.txt" as well.
Except for git-format-patch.txt which includes the former but not
the latter. But this is inside ifndef::git-format-patch[], so the
above description being a bit imprecise does not cause any actual
damage.
Documentation for all commands that want to describe the `-p`
option by including the "diff-options.txt" file also include the
"diff-generate-patch.txt" file, so an internal link would work
for all of them.
or something like that, perhaps.
> Next, when formatted as man-page, the section title is rendered
> "GENERATING PATCH TEXT WITH -P" whereas reference still reads
> "Generating patch text with -p", that is both inconsistent and makes
> searching harder than it needs to be.
>
> Fix the issues by just referring to the section, without custom
> reference text, and then unconditionally.
That does make sense.
> Fixes: ebdc46c242 (docs: link generating patch sections)
> Signed-off-by: Sergey Organov <sorganov@gmail.com>
> ---
> Documentation/diff-options.txt | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
> index 9f33f887711d..c07488b123c6 100644
> --- a/Documentation/diff-options.txt
> +++ b/Documentation/diff-options.txt
> @@ -22,13 +22,7 @@ ifndef::git-format-patch[]
> -p::
> -u::
> --patch::
> - Generate patch (see section titled
> -ifdef::git-log[]
> -<<generate_patch_text_with_p, "Generating patch text with -p">>).
> -endif::git-log[]
> -ifndef::git-log[]
> -"Generating patch text with -p").
> -endif::git-log[]
> + Generate patch (see <<generate_patch_text_with_p>>).
> ifdef::git-diff[]
> This is the default.
> endif::git-diff[]
next prev parent reply other threads:[~2023-09-05 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 17:52 [PATCH 1/1] doc/diff-options: fix link to generating patch section Sergey Organov
2023-09-05 22:49 ` Junio C Hamano [this message]
2023-09-06 6:40 ` Sergey Organov
2023-09-06 6:47 ` Sergey Organov
2023-09-06 15:58 ` Junio C Hamano
2023-09-06 7:15 ` [PATCH v2 " Sergey Organov
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=xmqq34zsqlr3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=johncai86@gmail.com \
--cc=sorganov@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).