Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345409 - Compare with "Branch, Tag, or Reference..." doesn't allow editing
Summary: Compare with "Branch, Tag, or Reference..." doesn't allow editing
Status: VERIFIED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.12   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Sawicki CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 334998 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-11 08:26 EDT by James Blackburn CLA
Modified: 2013-09-27 12:24 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Blackburn CLA 2011-05-11 08:26:54 EDT 
Eclipse EGit (Incubation)	0.12.0.201103251413	org.eclipse.egit.feature.group
  Eclipse JGit (Incubation)	0.12.0.201103250414	org.eclipse.jgit.feature.group

While editing a source file, if I right click > Compare with HEAD Revision I can edit my local file.  However if instead I compare with the another branch, I am unable to edit my local copy.
Comment 1 Markus Keller CLA 2011-09-27 09:46:18 EDT 
Yep, the left editor should be the local file. Then you should also get the "Open" and "Show In" context menu items for free.
Comment 2 Markus Keller CLA 2011-10-23 17:32:07 EDT 
When I do Compare With > History... and then compare a history entry with the working tree, then I do get the editable local file on the left.

Would be a great timesaver if I wouldn't have to use this workaround.
Comment 3 Kevin Sawicki CLA 2011-11-08 20:27:52 EST 
Proposed fix pushed to: http://egit.eclipse.org/r/4577
Comment 4 Stefan Lay CLA 2011-11-09 05:04:29 EST 
Fixed with c8f751eeddc592e77075a9424b4ba559003adcf5
Comment 5 Dani Megert CLA 2011-11-10 03:28:55 EST 
Verified in 1.2.0.201111100222.
Comment 6 Robin Stocker CLA 2013-09-27 12:24:38 EDT 
*** Bug 334998 has been marked as a duplicate of this bug. ***