git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Find successor of common ancestor

From
Avery Pennarun <apenwarr@gmail.com>
Date
Jul 16, 2010, 15:44 UTC
Message-ID
<AANLkTiloDCX4SuEDe_BNivv3UkY2TrQU1EAZlZGd1HYs@mail.gmail.com>
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
Previous: Andreas Schwab
Message 7 of 7 in “Find successor of common ancestor”
  1. Enrico WeigeltJul 16, 2010
  2. Santi BéjarJul 16, 2010
  3. Enrico WeigeltJul 16, 2010
  4. Johan HerlandJul 16, 2010
  5. Enrico WeigeltJul 16, 2010
  6. Andreas SchwabJul 16, 2010
  7. Avery PennarunJul 16, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.