From: Junio C Hamano <gitster@pobox.com>
To: Han Young <hanyang.tony@bytedance.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2] show doc: redirect user to git log manual instead of git diff-tree
Date: Wed, 20 Sep 2023 08:52:30 -0700 [thread overview]
Message-ID: <xmqqpm2calkx.fsf@gitster.g> (raw)
In-Reply-To: <20230920132731.1259-1-hanyang.tony@bytedance.com> (Han Young's message of "Wed, 20 Sep 2023 21:27:31 +0800")
Han Young <hanyang.tony@bytedance.com> writes:
> While git show accepts options that apply to the git diff-tree command,
> some options do not make sense in the context of git show.
> The options of git show are handled using the machinery of git log.
> The git log manual page is a better place to look into than git diff-tree
> for options that are not in the git show manual page.
>
> Signed-off-by: Han Young <hanyang.tony@bytedance.com>
> ---
> Changes since v1:
> * change wording to clarify not all options of `git log` are meant for `git show`
Nice. Thank you very much for not forgetting this topic.
> Documentation/git-show.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/git-show.txt b/Documentation/git-show.txt
> index 2b1bc7288d..fc46b3687b 100644
> --- a/Documentation/git-show.txt
> +++ b/Documentation/git-show.txt
> @@ -26,7 +26,7 @@ with --name-only).
>
> For plain blobs, it shows the plain contents.
>
> -The command takes options applicable to the 'git diff-tree' command to
> +Some options that 'git log' command understands can be used to
> control how the changes the commit introduces are shown.
>
> This manual page describes only the most frequently used options.
prev parent reply other threads:[~2023-09-20 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 12:12 [PATCH] show doc: redirect user to git log manual instead of git diff-tree Han Young
2023-09-05 23:26 ` Junio C Hamano
2023-09-06 6:09 ` Han Young
2023-09-06 17:26 ` Junio C Hamano
2023-09-20 13:27 ` [PATCH v2] " Han Young
2023-09-20 15:52 ` 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=xmqqpm2calkx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hanyang.tony@bytedance.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).