{"thread":{"id":"2961","subject":"Recursive merge still doesn't handle reorganized repositories","startedAt":"2006-01-04T01:58:50Z","lastAt":"2006-01-04T01:58:50Z","messageCount":1,"participants":["H. Peter Anvin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14157","messageId":"43BB2BDA.6070404@zytor.com","threadId":"2961","inReplyTo":null,"subject":"Recursive merge still doesn't handle reorganized repositories","fromName":"H. Peter Anvin","fromEmail":"hpa@zytor.com","sentAt":"2006-01-04T01:58:50Z","receivedAt":"2006-01-04T01:58:50Z","isPatch":false,"sender":{"key":"hpa@zytor.com","avatar":null},"body":"Well, I got the chance to try out \"git-merge -s recursive\" to try to \ndeal with the two different reorganized klibc repositories.  I'm sad to \nreport that it doesn't really work, and that every merge has to be \npropagated manually.\n\nThe two repos are at:\n\n\tgit://git.kernel.org/pub/scm/libs/klibc/klibc.git\n\tgit://git.kernel.org/pub/scm/libs/klibc/klibc-renamed.git\n\t\nWhat I want is for a change to the first to propagate naturally to the \nsecond.\n\n\t-hpa\n"}]}