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

Re: Incorrect pipe for git log graph when using --name-status option

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 13, 2017, 19:25 UTC
Message-ID
<xmqqa89pevw0.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CAM_JFCwYAKCWrHqCtcwid27V1HvhuSmp4QpbNpgyMzrzWUNYog@mail.gmail.com>
hIpPy <hippy2981@gmail.com> writes:
Show 14 quoted lines
> The `git log` command with `graph` and pretty format works correctly
> as expected.
>
> $ git log --graph --pretty=format:'%h' -2
> * 714a14e
> * 87dce5f
>
>
> However, with `--name-status` option added, there is a pipe
> incorrectly placed after the commit hash (example below).
>
> $ git log --graph --pretty=format:'%h' -2 --name-status
> * 714a14e|
> | M README.md

Is it a --name-status, or is it your own custom format, that is causing the above issue?

 - What happens if you stop using --pretty=format:%h and replace it
   with something like --oneline?
 - What happens if you keep using --pretty=format:%h but replace
   --name-status with something else, e.g. --raw or --stat?
Previous: hIpPyNext: hIpPy
Message 2 of 8 in “Incorrect pipe for git log graph when using --name-status option”
  1. hIpPyFeb 13, 2017
  2. Junio C HamanoFeb 13, 2017
  3. hIpPyFeb 13, 2017
  4. Jeff KingFeb 13, 2017
  5. Junio C HamanoFeb 13, 2017
  6. Jeff KingFeb 13, 2017
  7. hIpPyFeb 13, 2017
  8. Jeff KingFeb 13, 2017

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.