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

git & svn related merge questions ...

From
SRSaurabh Raje <saurabh.raje@gmail.com>
Date
Jun 17, 2008, 11:28 UTC
Message-ID
<loom.20080617T112816-101@post.gmane.org>
Hi All,
I have a question regarding 3-way merge ...
Here's how the subversion commits had happened
- Initially we had 'trunk' at revision T1
- We made a 'branch' (svn cp) at revision B1 (T1 -> B1)
(...development continues in trunk & branch...)
- We merge (svn merge) changes T2 - T1 in branch B2 and resolve all the
conflicts (if any) committing revision B3
(...development continues in trunk...)

After this I imported the entire subversion repository in Git (git-svn clone) & then tried to merge the 'branch' (@B3) in 'trunk' (@T3).

The problem here is that the common ancestor is considered as T1 for 'trunk' & branch' & not T2 which causes many more merge conflicts which should not have been there ... In subversion flow we used to merge diff of branch@B3 and trunk@T2 in trunk to achieve the result with minimum conflicts.

Any idea of how to fix this?

I just started using Git. It is a fantastic piece of software. Thank you all.

Regards,
Saurabh Raje 
Message 1 of 1 in “git & svn related merge questions ...”
  1. Saurabh RajeJun 17, 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.