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

Recursive merge still doesn't handle reorganized repositories

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Jan 4, 2006, 01:58 UTC
Message-ID
<43BB2BDA.6070404@zytor.com>

Well, I got the chance to try out "git-merge -s recursive" to try to deal with the two different reorganized klibc repositories. I'm sad to report that it doesn't really work, and that every merge has to be propagated manually.

The two repos are at:
	git://git.kernel.org/pub/scm/libs/klibc/klibc.git
	git://git.kernel.org/pub/scm/libs/klibc/klibc-renamed.git
	
What I want is for a change to the first to propagate naturally to the 
second.
	-hpa
Message 1 of 1 in “Recursive merge still doesn't handle reorganized repositories”
  1. H. Peter AnvinJan 4, 2006

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.