From: Miklos Vajna <vmiklos@frugalware.org>
To: Elijah Newren <newren@gmail.com>
Cc: bd@bc-bd.org, git@vger.kernel.org
Subject: Re: How do I show only log messages for commits on a specific branch?
Date: Thu, 17 Dec 2009 00:26:42 +0100 [thread overview]
Message-ID: <20091216232641.GK25474@genesis.frugalware.org> (raw)
In-Reply-To: <51419b2c0912161005n1596d4a1n92ed555c98aee4c6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Wed, Dec 16, 2009 at 11:05:52AM -0700, Elijah Newren <newren@gmail.com> wrote:
> git log new@{30.years.ago}..new
> (You'll get a warning that 'new' hasn't existed for 30 years but it
> doesn't hurt anything)
That's the same as "git log new", if I'm not mistaken.
What Stefan wants to do is to let git log show the commits which are
only in the "new" branch, but I don't think there is an out-of-the-box
solution for that.
One solution I can think of is to iterate over each ref using "git
for-each-ref --format='%(refname)' 'refs/heads/*'", then run "git
merge-base $i new", run git rev-list $mb..new|wc -l and then you could
decide what is the first commit that does not belong to any other
branch. But that's just an idea, I don't have the motivation to script
it properly.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-12-16 23:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 10:16 How do I show only log messages for commits on a specific branch? bd
2009-12-16 18:05 ` Elijah Newren
2009-12-16 23:26 ` Miklos Vajna [this message]
2009-12-16 23:58 ` Santi Béjar
2009-12-17 0:04 ` Elijah Newren
2009-12-16 23:59 ` Elijah Newren
2009-12-17 0:20 ` Miklos Vajna
2009-12-17 14:20 ` Stefan Völkel
2009-12-17 9:20 ` David Roden
2009-12-17 15:04 ` Pat Notz
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=20091216232641.GK25474@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=bd@bc-bd.org \
--cc=git@vger.kernel.org \
--cc=newren@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox