* [bug?] renamed file loses changes in merge.
@ 2015-02-24 15:33 Mauro Condarelli
0 siblings, 0 replies; only message in thread
From: Mauro Condarelli @ 2015-02-24 15:33 UTC (permalink / raw)
To: git
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-02-24 15:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-02-24 15:33 [bug?] renamed file loses changes in merge Mauro Condarelli
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).