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

Re: Direct ancestors from commit to HEAD

From
Jakub Narebski <jnareb@gmail.com>
Date
Sep 16, 2009, 14:26 UTC
Message-ID
<m3vdjj2ceq.fsf@localhost.localdomain>
In-Reply-To
<4AB0EFC0.8020005@googlemail.com>
Gonsolo <gonsolo@gmail.com> writes:
Show 27 quoted lines
> Is there a way to see only the direct line of (merge) ancestors from
> patch to HEAD? Something like:
> 
> commit 0cb583fd2862f19ea88b02eb307d11c09e51e2f8
> Merge: 723e9db... a2d1056...
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Tue Sep 15 10:01:16 2009 -0700
> 
> 	Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6
> 
> commit 88512935a24305fea7aecc9ba4d675869e97fc2a
> Merge: 8a62bab... 6b26dea...
> Author: David S. Miller <davem@davemloft.net>
> Date:   Fri Aug 14 12:27:19 2009 -0700
> 
> 	Merge branch 'master' of
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6
> 
> commit edd7fc7003f31da48d06e215a93ea966a22c2a03
> Author: Nick Kossifidis <mick@madwifi-project.org>
> Date:   Mon Aug 10 03:29:02 2009 +0300
> 
>      ath5k: Wakeup fixes
> 
> 
> Here I can see exactly how the ath5k patch came to mainline and since
> when it is there.

I don't know whether --first-parent or --simplify-by-decoration, or perhaps --dense is what you want (you can also use --graph for better visualization).

Or use git-show-branch... :-)
-- 
Jakub Narebski
Poland
ShadeHawk on #git
Previous: GonsoloNext: Gonsolo
Message 2 of 3 in “Direct ancestors from commit to HEAD”
  1. GonsoloSep 16, 2009
  2. Jakub NarebskiSep 16, 2009
  3. GonsoloSep 16, 2009

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.