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

merging branches with separate but identical history

From
Craig de Stigter <craig.destigter@koordinates.com>
Date
Aug 31, 2010, 21:01 UTC
Message-ID
<AANLkTikTzZe=c=RaEYSr_wjfHht4PZihggnV9vEOehvy@mail.gmail.com>
In-Reply-To
<AANLkTikoDkhKTRmob=B_NYJSYoby0J3Zo-Qp43AU9WfZ@mail.gmail.com>
Hi list

I have two branches which start with the same commits, and I want to merge them. I believe the two branches were individually pulled from the same SVN repo, so they look like this:

branch1: a--b--c--d--e--f--1--3--5 branch2: a--b--c--d--e--f--2--4--6

If I do:
> git checkout branch1
> git merge branch2
Merge made by recursive
The merge succeeds but the commits in each branch aren't squashed
together (git log shows two commits for each actual commit)
 i.e., now my history looks like this:
a--a--b--b--c--c--d--d--e--e--f--f--1--2--3--4--5--6

Is there a way to do this without the duplicates? (perhaps a way to mark the branch as merged up to 'f', without actually performing a merge?)

Thanks Craig de Stigter -- Koordinates Ltd PO Box 1604, Shortland St, Auckland, New Zealand Phone +64-9-966 0433 Fax +64-9-969 0045 Web http://www.koordinates.com

Next: Jonathan Nieder
Message 1 of 3 in “merging branches with separate but identical history”
  1. Craig de StigterAug 31, 2010
  2. Jonathan NiederAug 31, 2010
  3. Henrik GrubbströmSep 1, 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.