Re: `git show --oneline commit` does not do what's intuitively expected

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Feb 22, 2017, 17:18 UTC
Message-ID: <CAADWXX_S8RWE7pSZ-2JM_JeNT7LfHFgEopt6SUUUQYx0yumojw@mail.gmail.com>
In-Reply-To: <20170217040522.jugt4uuak74l3qjw@sigill.intra.peff.net>

On Thu, Feb 16, 2017 at 8:05 PM, Jeff King <peff@peff.net> wrote:

Show 6 quoted lines

> On Fri, Feb 17, 2017 at 02:51:36AM +0100, Luna Kid wrote:
>
>> tl;dr; --> Please add --no-diff (or --msg-only) to git show. We'll
>> love you for that. :)
>
> I think it is already spelled "--no-patch", or "-s" for short.

I think people should also learn about "--no-walk" (or the numberic walk limiters) to the revision walking logic, because it can often be useful.

IOW, if you only want the commit info, you can certainly use "git show -s", but you can also use

    git log --no-walk .. list of commits ..

or

    git log -1 <single-commit>

to show a commit without any other details.

Basically, "git show" for a commit does what is mostly equivalent to

     git log --cc --no-walk

although "git show" then has other features too (ie it shows non-commits etc).

                Linus