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

Re: Find successor of common ancestor

From
SBSanti Béjar <santi@agolina.net>
Date
Jul 16, 2010, 08:49 UTC
Message-ID
<AANLkTintIToGZu3fvK4aE5LFL7MgOnlfwKgsZ79Q0-o1@mail.gmail.com>
In-Reply-To
<20100716082937.GA22894@nibiru.local>
On Fri, Jul 16, 2010 at 10:29 AM, Enrico Weigelt <weigelt@metux.de> wrote:
Show 10 quoted lines
>
> 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).
This is just what "git rebase"  does:

$ git checkout B' $ git rebase A'

HTH, Santi

Previous: Enrico WeigeltNext: Enrico Weigelt
Message 2 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.