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, 01:28 UTC
Message-ID
<7vwsxaxt5j.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0707090214280.4248@racer.site>
Sorry, not 88494239 but this one.
commit 884944239f2ab673cedfaa5e7999d31fd6a46331
Author: Junio C Hamano <junkio@cox.net>
Date:   Sun Jan 29 15:24:42 2006 -0800
    rev-list: omit duplicated parents.
    
    Showing the same parent more than once for a commit does not
    make much sense downstream, so stop it.
    
    This can happen with an incorrectly made merge commit that
    merges the same parent twice, but can happen in an otherwise
    sane development history while squishing the history by taking
    into account only commits that touch specified paths.
    
    For example,
    
    	$ git rev-list --max-count=1 --parents addafaf -- rev-list.c
    
    would have to show this commit ancestry graph:
    
                      .---o---.
                     /         \
                    .---*---o---.
                   /    93b74bc  \
       ---*---o---o-----o---o-----o addafaf
          d8f6b34  \             /
                    .---o---o---.
                     \         /
                      .---*---.
                          3815f42
    
    where 5 independent development tracks, only two of which have
    changes in the specified paths since they forked.  The last
    change for the other three development tracks was done by the
    same commit before they forked, and we were showing that three
    times.
    
    Signed-off-by: Junio C Hamano <junkio@cox.net>
Previous: Johannes SchindelinNext: Junio C Hamano
Message 5 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.