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

Re: Push merges?

From
Jeff King <peff@peff.net>
Date
Mar 27, 2008, 03:09 UTC
Message-ID
<20080327030935.GA4974@coredump.intra.peff.net>
In-Reply-To
<ba5eca00803261452r4b5a7b6bi600c30e79b945477@mail.gmail.com>
On Wed, Mar 26, 2008 at 02:52:06PM -0700, Ryan Leigh wrote:
Show 7 quoted lines
> I've been getting to know git and I've stumbled across a "problem" and
> I haven't yet been able to find a solution. For example, say I have a
> branch "base" and two branches of that "foo" and "bar". I make some
> change in "base", commit it, and now I would like to have it in both
> "foo" and "bar". Is there a command that rather than get another
> branch and merge with the current branch will instead take the current
> branch and apply a merge on other branches? I've done google searches

No, there isn't such a command. Merges must be done one at a time because they use the index and working tree to report conflicts.

So what you are asking for is the moral equivalent of:
  for i in foo bar; do
    git checkout $i && git merge master
  done

and you could do it that way, except that the 'merge' step may fail with conflicts that need to be fixed up by hand.

-Peff
Previous: Ryan Leigh
Message 2 of 2 in “Push merges?”
  1. Ryan LeighMar 26, 2008
  2. Jeff KingMar 27, 2008

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.