From: Avery Pennarun <apenwarr@gmail.com>
To: weigelt@metux.de
Cc: git@vger.kernel.org
Subject: Re: Find successor of common ancestor
Date: Fri, 16 Jul 2010 11:44:40 -0400 [thread overview]
Message-ID: <AANLkTiloDCX4SuEDe_BNivv3UkY2TrQU1EAZlZGd1HYs@mail.gmail.com> (raw)
In-Reply-To: <20100716082937.GA22894@nibiru.local>
On Fri, Jul 16, 2010 at 4:29 AM, Enrico Weigelt <weigelt@metux.de> wrote:
> I've forked some branch A into B, now A and B have evolved
> independently for quite some time into A' and B'. Now I'd like
> to rebase B' along A' history line step by step - first on A+1,
> then A+3, ... until A' (that's what I'd call zip-rebase).
You haven't *really* explained what you want to do here, but that
doesn't really effect the answer to your actual question...
> For this I need to find out the successor commit A (along the A'
> history line). Does anyone know how to do that ?
git rev-list --first-parent --reverse $(git merge-base A B)..A
Have fun,
Avery
prev parent reply other threads:[~2010-07-16 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 8:29 Find successor of common ancestor Enrico Weigelt
2010-07-16 8:49 ` Santi Béjar
2010-07-16 9:06 ` Enrico Weigelt
2010-07-16 12:19 ` Johan Herland
2010-07-16 15:35 ` Enrico Weigelt
2010-07-16 12:29 ` Andreas Schwab
2010-07-16 15:44 ` Avery Pennarun [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=AANLkTiloDCX4SuEDe_BNivv3UkY2TrQU1EAZlZGd1HYs@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=weigelt@metux.de \
/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).