From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'git'" <git@vger.kernel.org>
Cc: "'Phil Hord'" <phil.hord@gmail.com>
Subject: RE: Trouble merging renamed but identical files - CONFLICT (rename/rename)
Date: Sun, 29 Jun 2014 16:20:22 -0400 [thread overview]
Message-ID: <35E240FD8DD74A2F9B80FFCBD818A122@black> (raw)
In-Reply-To: <CABURp0qZVMGMQ8X4P0P1OGF9gNqu__=Uk+Lr7GyBbscm5wL1=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
> -----Original Message-----
> From: Phil Hord
> Sent: Sunday, June 29, 2014 16:09
>
> On Sun, Jun 29, 2014 at 11:31 AM, Phil Hord
> <phil.hord@gmail.com> wrote:
> > On Fri, Jun 27, 2014 at 8:42 PM, Jason Pyeron
> <jpyeron@pdinc.us> wrote:
> >> Sorry for the http://pastebin.com/1R68v6jt (changes the merge to
> >> 1ca13ed2271d60ba93d40bcc8db17ced8545f172, and manually
> reconciles the merge),
> >> but it was too long to be readable in the email.
>
> Ok, I think I understand the issue you are trying to solve now.
>
> Git (rather famously[1]) does not record renames or copies. It is
> expected instead that renames and copies will be detected when it is
> important after the fact. This allows us to ignore rename detection
> and resolution when creating project history; in the future, better
> rename/copy detection will "just work" on existing repositories and
> the repos themselves will not need to be adjusted.
Looking at http://pastebin.com/1R68v6jt , I have a work around.
In summary, 7.git cherry-pick -x HEAD..rebranding , then
git merge $(echo 'Merge of 1ca13ed2271d60ba93d40bcc8db17ced8545f172 branch -
rebranding' |\
git commit-tree -p HEAD -p rebranding \
$(git cat-file -p HEAD | grep ^tree | sed -e 's/^tree //') )
Now it is perfect in the blame and log --graph.
>
> What you are encountering now seems to be a shortcoming of Git's
> current rename/copy detection. But you are trying to overcome today's
> shortcoming by adjusting your project history to accommodate it.
> Instead you should just do the merge like you normally would without
> regard to how 'git blame' shows the result.
>
> Maybe there is a bug here still, but it is probably in git-blame.
>
> [1]
> https://git.wiki.kernel.org/index.php/GitFaq#Why_does_Git_not_
> .22track.22_renames.3F
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6748 bytes --]
next prev parent reply other threads:[~2014-06-29 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 20:47 Trouble merging renamed but identical files - CONFLICT (rename/rename) Jason Pyeron
2014-06-27 21:46 ` Phil Hord
2014-06-27 22:39 ` Jason Pyeron
2014-06-29 15:28 ` Phil Hord
[not found] ` <66A60DA77398CD439FA676CEF593977D52477A@exchange.1.internal.pdinc.us>
2014-06-28 0:42 ` Jason Pyeron
2014-06-28 9:46 ` Jason Pyeron
2014-06-29 15:31 ` Phil Hord
2014-06-29 20:09 ` Phil Hord
2014-06-29 20:20 ` Jason Pyeron [this message]
2014-06-29 20:26 ` Phil Hord
2014-06-29 21:13 ` Jason Pyeron
2014-06-30 1:42 ` Phil Hord
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=35E240FD8DD74A2F9B80FFCBD818A122@black \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=phil.hord@gmail.com \
/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