From: Junio C Hamano <gitster@pobox.com>
To: Howard Miller <howard@e-learndesign.co.uk>
Cc: git@vger.kernel.org
Subject: Re: Comparing commits on two different branches
Date: Mon, 05 Mar 2012 09:38:24 -0800 [thread overview]
Message-ID: <7vr4x70wz3.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAHVO_92V3rRBngrZMLeq17ekKKB41kTmok39uUeZ6aOzxB65dQ@mail.gmail.com> (Howard Miller's message of "Mon, 5 Mar 2012 16:18:51 +0000")
Howard Miller <howard@e-learndesign.co.uk> writes:
> I have two branches - I know that one differs from the other entirely
> by a (large) number of commits that I have made over some time.
> Unfortunately, these are now all mixed up with a load of other commits
> that have been merged into both from the upstream project.
"now all mixed up" makes me feel a lot less optimistic, but have you
tried git-cherry?
prev parent reply other threads:[~2012-03-05 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 16:18 Comparing commits on two different branches Howard Miller
2012-03-05 17:38 ` Junio C Hamano [this message]
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=7vr4x70wz3.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=howard@e-learndesign.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).