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

Re: Bug in "git log --graph -p -m" (version 1.7.7.6)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 5, 2013, 17:40 UTC
Message-ID
<7vtxpqslpm.fsf@alter.siamese.dyndns.org>
In-Reply-To
<201302051700.r15H0GXx031004@freeze.ariadne.com>
worley@alum.mit.edu (Dale R. Worley) writes:
> I have found a situation where "git log" produces (apparently)
> endless output.  Presumably this is a bug.  Following is a (Linux)
> script that reliably reproduces the error for me (on Fedora 16):
Wasn't this fixed at v1.8.1.1~13 or is this a different issue?
Previous: Dale R. WorleyNext: Matthieu Moy
Message 2 of 9 in “Bug in "git log --graph -p -m" (version 1.7.7.6)”
  1. Dale R. WorleyFeb 5, 2013
  2. Junio C HamanoFeb 5, 2013
  3. Matthieu MoyFeb 5, 2013
  4. Dale R. WorleyFeb 6, 2013
  5. John KeepingFeb 6, 2013
  6. Matthieu MoyFeb 6, 2013
  7. graph: output padding for merge subsequent parentsJohn Keeping, Feb 6, 2013
  8. Matthieu MoyFeb 8, 2013
  9. Junio C HamanoFeb 8, 2013

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.