Bug 197482 - [Actions] Action named Compare with Head while working on a branch
Summary: [Actions] Action named Compare with Head while working on a branch
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-23 09:27 EDT by Tomasz Zarna CLA
Modified: 2019-09-06 16:16 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2007-07-23 09:27:35 EDT
Build ID: N20070714-0010

Steps To Reproduce:
1. Share a project using CVS repository
2. Branch the project
3. Switch to the branch
4. Create a new, unmanaged file
5. Right click on it, select "Compare With" menu
=> First entry in the submenu is "Latest from HEAD". I expected to be able to compare with latest from the current branch not with head. Am I wrong?
Comment 1 Michael Valenta CLA 2007-07-24 11:53:11 EDT
Technically you are correct. In this particular case, the action name is not determined properly. I suspect the problem is that only the sync info for the selected resource is queried. In the case were a resource has no sync info, we could look at the parent. However, we need to be careful since this is happening in the code that shows the menu (i.e. we don't want to walk all the way up to the project level since this has performance implications). It would be interesting to know if the comparison actually was performed against head or if the action, when run, properly determined the tag. 

Anyway, I don't view this as a high priority since, in 99.9% of the cases, you would be comparing the resource with nothing since it is new.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:16:57 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.