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

Re: Changes based on a branch not yet merged back to master

From
Jeff King <peff@peff.net>
Date
Apr 8, 2014, 19:53 UTC
Message-ID
<20140408195309.GA8461@sigill.intra.peff.net>
In-Reply-To
<1396981364.85181.YahooMailNeo@web121903.mail.ne1.yahoo.com>
On Tue, Apr 08, 2014 at 11:22:44AM -0700, K. Kwan wrote:
Show 20 quoted lines
> My tree would look like this:
> 
> - x - x - x (master) 
> 
>        \ x - x (A) x - x (B)
> 
> 
> But after merge of branch (A), I would like it to look like this:
> 
> - x - x - x ---- x (master)
>        \        / \
>         x - x (A)  x - x (B)
> 
> 
> Perhaps this?
> 
> $ git checkout master
> $ git pull origin master
> $ git merge A
> $ git rebase --onto master A B
Yes, that should work. I think you could even just do:
  git rebase master B

since after the merge, all of A is contained in master (and so will be omitted from the rebased commits).

-Peff
Previous: K. Kwan
Message 2 of 2 in “Changes based on a branch not yet merged back to master”
  1. K. KwanApr 8, 2014
  2. Jeff KingApr 8, 2014

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.