From: Junio C Hamano <gitster@pobox.com>
To: Denton Liu <liu.denton@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-diff: fix missing --merge-base docs
Date: Mon, 12 Jul 2021 13:52:19 -0700 [thread overview]
Message-ID: <xmqqlf6b2r24.fsf@gitster.g> (raw)
In-Reply-To: <f0e7ef2433e2836fed579f2765654c5f97d5d778.1625909286.git.liu.denton@gmail.com> (Denton Liu's message of "Sat, 10 Jul 2021 02:28:31 -0700")
Denton Liu <liu.denton@gmail.com> writes:
> When `git diff --merge-base` was introduced, the documentation included
> a few errors.
>
> In the example given for `git diff --cached --merge-base`, the
> `--cached` flag was omitted for the `--merge-base` example. Add the
> missing flag.
>
> In the `git diff <commit>` case, we failed to mention that
> `--merge-base` is an available option. Give the usage of `--merge-base`
> as an option there.
>
> Finally, there are two errors in the usage of `git diff`. Firstly, we do
> not mention `--merge-base` in the `git diff --cached` case. Mention it
> so that it's consistent with the documentation. Secondly, we put the
> `[--merge-base]` in between `<commit>` and `[<commit>...]`. Move the
> `[--merge-base]` so that it's beside `[<options>]` which is a more
> logical grouping.
>
> Signed-off-by: Denton Liu <liu.denton@gmail.com>
> ---
> Documentation/git-diff.txt | 10 +++++++---
> builtin/diff.c | 4 ++--
> 2 files changed, 9 insertions(+), 5 deletions(-)
Thanks. Both hunks look sensible.
>
> diff --git a/Documentation/git-diff.txt b/Documentation/git-diff.txt
> index 7f4c8a8ce7..6236c75c9b 100644
> --- a/Documentation/git-diff.txt
> +++ b/Documentation/git-diff.txt
> @@ -51,16 +51,20 @@ files on disk.
> --staged is a synonym of --cached.
> +
> If --merge-base is given, instead of using <commit>, use the merge base
> -of <commit> and HEAD. `git diff --merge-base A` is equivalent to
> -`git diff $(git merge-base A HEAD)`.
> +of <commit> and HEAD. `git diff --cached --merge-base A` is equivalent to
> +`git diff --cached $(git merge-base A HEAD)`.
>
> -'git diff' [<options>] <commit> [--] [<path>...]::
> +'git diff' [<options>] [--merge-base] <commit> [--] [<path>...]::
>
> This form is to view the changes you have in your
> working tree relative to the named <commit>. You can
> use HEAD to compare it with the latest commit, or a
> branch name to compare with the tip of a different
> branch.
> ++
> +If --merge-base is given, instead of using <commit>, use the merge base
> +of <commit> and HEAD. `git diff --merge-base A` is equivalent to
> +`git diff $(git merge-base A HEAD)`.
>
> 'git diff' [<options>] [--merge-base] <commit> <commit> [--] [<path>...]::
>
> diff --git a/builtin/diff.c b/builtin/diff.c
> index 2d87c37a17..dd8ce688ba 100644
> --- a/builtin/diff.c
> +++ b/builtin/diff.c
> @@ -26,8 +26,8 @@
>
> static const char builtin_diff_usage[] =
> "git diff [<options>] [<commit>] [--] [<path>...]\n"
> -" or: git diff [<options>] --cached [<commit>] [--] [<path>...]\n"
> -" or: git diff [<options>] <commit> [--merge-base] [<commit>...] <commit> [--] [<path>...]\n"
> +" or: git diff [<options>] --cached [--merge-base] [<commit>] [--] [<path>...]\n"
> +" or: git diff [<options>] [--merge-base] <commit> [<commit>...] <commit> [--] [<path>...]\n"
> " or: git diff [<options>] <commit>...<commit>] [--] [<path>...]\n"
> " or: git diff [<options>] <blob> <blob>]\n"
> " or: git diff [<options>] --no-index [--] <path> <path>]\n"
prev parent reply other threads:[~2021-07-12 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 9:28 [PATCH] git-diff: fix missing --merge-base docs Denton Liu
2021-07-12 20: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=xmqqlf6b2r24.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=liu.denton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.