From: Jakub Narebski <jnareb@gmail.com>
To: Gonsolo <gonsolo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Direct ancestors from commit to HEAD
Date: Wed, 16 Sep 2009 07:26:41 -0700 (PDT) [thread overview]
Message-ID: <m3vdjj2ceq.fsf@localhost.localdomain> (raw)
In-Reply-To: <4AB0EFC0.8020005@googlemail.com>
Gonsolo <gonsolo@gmail.com> writes:
> 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
next prev parent reply other threads:[~2009-09-16 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 14:01 Direct ancestors from commit to HEAD Gonsolo
2009-09-16 14:26 ` Jakub Narebski [this message]
2009-09-16 15:10 ` Gonsolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vdjj2ceq.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gonsolo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.