From: Mauro Condarelli <mc5686@mclink.it>
To: git@vger.kernel.org
Subject: [bug?] renamed file loses changes in merge.
Date: Tue, 24 Feb 2015 16:33:42 +0100 [thread overview]
Message-ID: <54EC99D6.9010307@mclink.it> (raw)
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
reply other threads:[~2015-02-24 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54EC99D6.9010307@mclink.it \
--to=mc5686@mclink.it \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).