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

Re: [PATCH] Fix "git log --parent -m" from emitting duplicated parent info

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 9, 2007, 00:37 UTC
Message-ID
<7vd4z2za2g.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<e5bfff550707080737j56c161bdrf0c079b61877085b@mail.gmail.com>

This is whitespace damaged in a funny way (some lines do not have leading whitespace while some do).

log_tree_diff() hence log_tree_commit() is caled by codepaths other than "git log -p", and I am not convinced that this patch would not break them. Worrysome.

I wonder why we did not actually remove the duplicate parents from "commit->parents" list after history simplification when we originally did 88494239, instead of filtering only on the output path. Anybody remember the reason?

Previous: Junio C HamanoNext: Johannes Schindelin
Message 3 of 10 in “Fix "git log --parent -m" from emitting duplicated parent info”
  1. Fix "git log --parent -m" from emitting duplicated parent infoMarco Costalba, Jul 8, 2007
  2. Junio C HamanoJul 8, 2007
  3. Junio C HamanoJul 9, 2007
  4. Johannes SchindelinJul 9, 2007
  5. Junio C HamanoJul 9, 2007
  6. Junio C HamanoJul 9, 2007
  7. Johannes SchindelinJul 9, 2007
  8. Junio C HamanoJul 9, 2007
  9. Marco CostalbaJul 9, 2007
  10. Junio C HamanoJul 9, 2007

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.