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

[bug?] renamed file loses changes in merge.

From
MCMauro Condarelli <mc5686@mclink.it>
Date
Feb 24, 2015, 15:33 UTC
Message-ID
<54EC99D6.9010307@mclink.it>
I'm unsure it is a bug or a misuse on my part, but:
Situation:

There are two distinct repositories (upstream & local), local is a fork of upstream (at tag "v3.7"). Both repositories were modified (upstream has delivered new version with tag "v3.7.1"). I need to incorporate local changes into the new upstream release.

I did the following:

git clone upstream git checkout v3.7.1 -b v3.7.1_local (I do not want anything later than that) git remote add local ../local/.git git fetch local git merge local/current ... resolve conflicts ... git ad --all git commit -m ...

At this point I discovered that one specific file: was renamed in upstream was changed in local

What I have on my workspace is the *renamed* file *without* the modifications from local.

Is this the normal behavior? If so I fail to understand the rationale behind it; I would expect git to apply changes to the renamed file.

Thanks in Advance Mauro

Message 1 of 1 in “[bug?] renamed file loses changes in merge.”
  1. Mauro CondarelliFeb 24, 2015

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.