From: Stefan Beller <sbeller@google.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: why do "git log -h" and "git show -h" print the same thing?
Date: Thu, 24 May 2018 15:42:58 -0700 [thread overview]
Message-ID: <CAGZ79kY8CjLsTqY2YXJ8hPA41XrbYZrtK7yO59vrbA5M_vorVg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1805240934010.12018@localhost.localdomain>
On Thu, May 24, 2018 at 6:37 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> maybe this is deliberate, but it's confusing that, with git 2.17.0,
> the output of both "git log -h" and "git show -h" is exactly the same:
>
> $ git log -h
> usage: git log [<options>] [<revision-range>] [[--] <path>...]
> or: git show [<options>] <object>...
>
> -q, --quiet suppress diff output
> --source show source
> --use-mailmap Use mail map file
> --decorate-refs <pattern>
> only decorate refs that match <pattern>
> --decorate-refs-exclude <pattern>
> do not decorate refs that match <pattern>
> --decorate[=...] decorate options
> -L <n,m:file> Process line range n,m in file, counting from 1
> $
>
> is that what's *supposed* to happen?
I would think so, show is just "log -p" with the range clamped
down to <object>^..<object>.
It's been in the code like that for a couple years by now,
e.g. see
e66dc0cc4b1a6 log.c: fix translation markings, 2015-01-06
next prev parent reply other threads:[~2018-05-24 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 13:37 why do "git log -h" and "git show -h" print the same thing? Robert P. J. Day
2018-05-24 22:42 ` Stefan Beller [this message]
2018-05-24 22:53 ` Robert P. J. Day
2018-05-27 10:24 ` Thomas Gummerer
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=CAGZ79kY8CjLsTqY2YXJ8hPA41XrbYZrtK7yO59vrbA5M_vorVg@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).