From: Enrico Weigelt <weigelt@metux.de>
To: git@vger.kernel.org
Subject: Find successor of common ancestor
Date: Fri, 16 Jul 2010 10:29:37 +0200 [thread overview]
Message-ID: <20100716082937.GA22894@nibiru.local> (raw)
Hi folks,
suppose the following situation:
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).
For this I need to find out the successor commit A (along the A'
history line). Does anyone know how to do that ?
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next reply other threads:[~2010-07-16 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 8:29 Enrico Weigelt [this message]
2010-07-16 8:49 ` Find successor of common ancestor 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
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=20100716082937.GA22894@nibiru.local \
--to=weigelt@metux.de \
--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 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).