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

Re: merge maintaining history

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 20, 2017, 17:33 UTC
Message-ID
<xmqqpojhy6tf.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<38ca43cb-2fc7-0448-352f-7d9413f815c5@gmail.com>
Jakub Narębski <jnareb@gmail.com> writes:
Show 10 quoted lines
> Then you would have the above history in repositories that fetched
> refs/replace/*, and the one below if replacement info is absent:
>
>    original A<-B<-C<-D<-E<-F<-----------M
>                 \                      /
>    first branch  b<-c<-d<-e           /
>                                      /
>    new repo               e*<-f->g->h
>
> But as Junio said it is highly unlikely that you are in this situation.

I do not think I said it is highly unlikely. I just said that I didn't read in what David wrote that he did some unusual things, so I based my conclusion on that assumption. People who bring problems here sometimes forget to tell crucial details, and that missing piece of information often changes how the situation should be handled.

Previous: Jakub NarębskiNext: David J. Bakeman
Message 6 of 9 in “merge maintaining history”
  1. David J. BakemanJan 14, 2017
  2. Jacob KellerJan 15, 2017
  3. David J. BakemanJan 19, 2017
  4. Junio C HamanoJan 19, 2017
  5. Jakub NarębskiJan 20, 2017
  6. Junio C HamanoJan 20, 2017
  7. David J. BakemanJan 26, 2017
  8. Jacob KellerJan 26, 2017
  9. Philip OakleyJan 19, 2017

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.