Bug 347663 - [client] Rename appears as outgoing delete and create in git status page
Summary: [client] Rename appears as outgoing delete and create in git status page
Status: RESOLVED WONTFIX
Alias: None
Product: Orion (Archived)
Classification: ECD
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on: 349168
Blocks:
  Show dependency tree
 
Reported: 2011-05-30 11:24 EDT by John Arthorne CLA
Modified: 2015-05-05 14:50 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Arthorne CLA 2011-05-30 11:24:29 EDT
I20110530

If you rename a file, it appears as an outgoing creation of the new file, and an outgoing deletion of the old file. It would be helpful to show this as a single rename, with the ability to open the compare diff showing any other changes to the file (similar to how the git command line handles it).

I don't think this is important for 0.2.
Comment 1 Missing name CLA 2011-10-05 04:53:46 EDT
I have the same problem. I rename a file in branch A, modify the same file in branch B, and then do a merge, the branches are not correctly merged.

With git commandline this works.
Comment 2 Tomasz Zarna CLA 2011-12-12 08:56:27 EST
"git mv" is nothing more than "mv {old} {new};git add {new};git rm {old}". In order this to work we would need to add some kind of a hook (something like org.eclipse.core.resources.team.TeamHook in Platform). Is there any other way?
Comment 3 John Arthorne CLA 2011-12-15 11:50:28 EST
With command line git this works without even using "git mv". I.e., if I move a file using Eclipse, command line, etc, then after adding the changes they show up in git status as moved. I assume they are using the file content hash to detect that they are the same file.
Comment 4 John Arthorne CLA 2015-05-05 14:50:38 EDT
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html