From: Jeff King <peff@peff.net>
To: "Nixon, Francis A" <francis.nixon17@imperial.ac.uk>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git Log ignores --oneline and --pretty=oneline in combination with -L.
Date: Tue, 28 Apr 2020 17:04:38 -0400 [thread overview]
Message-ID: <20200428210438.GD4000@coredump.intra.peff.net> (raw)
In-Reply-To: <DB8PR06MB6218D1398300AFD016D0B804D5AC0@DB8PR06MB6218.eurprd06.prod.outlook.com>
On Tue, Apr 28, 2020 at 02:28:15PM +0000, Nixon, Francis A wrote:
> Running `git log --pretty=oneline
> -L:get_stack_map_frames:stackmapframes.rs`(filename/function names as
> an example only, consistent across many files.) results on in correct
> output but doesn't ouput in a oneline format(still includes the full
> diffs).
The "--oneline" option has nothing to do with the diff display; it
controls the formatting of the commit message.
The default for git-log is not to show a diff at all, which is why "git
log --oneline" truly has only one line per commit. Using the "-L" option
implies showing a diff. Try adding "-s" or "--no-patch" to suppress it.
> Occurs on `git version 2.26.GIT`
> (e870325ee8575d5c3d7afe0ba2c9be072c692b65), as well as whatever `git
> version 2.20.1`.
Note that the combination of "-s" and "-L" was added in v2.22, so it
will work on one but not the other.
-Peff
prev parent reply other threads:[~2020-04-28 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 14:28 Git Log ignores --oneline and --pretty=oneline in combination with -L Nixon, Francis A
2020-04-28 21:04 ` Emma Brooks
2020-04-28 21:04 ` Jeff King [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=20200428210438.GD4000@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=francis.nixon17@imperial.ac.uk \
--cc=git@vger.kernel.org \
/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.