git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git Log ignores --oneline and --pretty=oneline in combination with -L.

From
Jeff King <peff@peff.net>
Date
Apr 28, 2020, 21:04 UTC
Message-ID
<20200428210438.GD4000@coredump.intra.peff.net>
In-Reply-To
<DB8PR06MB6218D1398300AFD016D0B804D5AC0@DB8PR06MB6218.eurprd06.prod.outlook.com>
On Tue, Apr 28, 2020 at 02:28:15PM +0000, Nixon, Francis A wrote:
Show 5 quoted lines
>  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
Previous: Emma Brooks
Message 3 of 3 in “Git Log ignores --oneline and --pretty=oneline in combination with -L.”
  1. Nixon, Francis AApr 28, 2020
  2. Emma BrooksApr 28, 2020
  3. Jeff KingApr 28, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.