From: Junio C Hamano <gitster@pobox.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: git@vger.kernel.org
Subject: Re: How to find commits unique to a branch
Date: Mon, 20 Jun 2016 15:21:20 -0700 [thread overview]
Message-ID: <xmqqtwgnsdr3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <878txz8ubq.fsf@thinkpad.rath.org> (Nikolaus Rath's message of "Mon, 20 Jun 2016 13:43:37 -0700")
Nikolaus Rath <Nikolaus@rath.org> writes:
> What's the best way to find all commits in a branch A that have not been
> cherry-picked from (or to) another branch B?
>
> I think I could format-patch all commits in every branch into separate
> files, hash the Author and Date of each files, and then compare the two
> lists. But I'm hoping there's a way to instead have git do the
> heavy-lifting?
"git cherry" perhaps?
next prev parent reply other threads:[~2016-06-20 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 20:43 How to find commits unique to a branch Nikolaus Rath
2016-06-20 22:21 ` Junio C Hamano [this message]
2016-06-20 23:21 ` Nikolaus Rath
2016-06-21 8:28 ` Michael J Gruber
2016-06-22 16:38 ` Nikolaus Rath
2016-06-21 18:04 ` Nikolaus Rath
2016-06-21 18:31 ` Junio C Hamano
2016-06-22 16:38 ` Nikolaus Rath
2016-06-22 18:20 ` Junio C Hamano
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=xmqqtwgnsdr3.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Nikolaus@rath.org \
--cc=git@vger.kernel.org \
/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.