Bug 323801 - Help user fixing problems in incoming changes
Summary: Help user fixing problems in incoming changes
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-27 06:19 EDT by Markus Keller CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2010-08-27 06:19:35 EDT
I20100824-1210

I often have a cursory look at incoming changes in the Synchronize view. When I see bugs in a change, I'd like to fix them right away. Unfortunately, Eclipse has no good story for this.

When I open an incoming change in a compare editor, I cannot edit the new (remote) version. To get a compare editor where I can edit the latest version, I have to perform these manual steps:

- remember the line number of the first problem I want to fix
- remember the base revision (from my workspace)
- update the file
- open history of the file
- find the base revision
- compare base revision with current
- find the first line that needs to be changed

That's too many steps for a common workflow.

Solution proposal:

When updating a file, check if there's already an open compare editor for that change (Local File on the left, Remote File on the right). That editor will be useless after the update, since both sides show the same content. The right side of the editor should be replaced with the original base version (which is also the Common Ancestor). Thus, the Update operation basically exchanges the left and the right side of the compare editor.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:07:49 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.