Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338051 - ambiguous destination ref
Summary: ambiguous destination ref
Status: RESOLVED DUPLICATE of bug 327600
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 0.11   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Lay CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-24 02:29 EST by CircleCode CLA
Modified: 2011-03-29 05:27 EDT (History)
1 user (show)

See Also:

Attachments
list of remotes (58.83 KB, image/png)
2011-03-28 10:20 EDT, CircleCode CLA 		no flags Details
team > synchronize wizard, showing the issue (120.22 KB, image/png)
2011-03-28 10:20 EDT, CircleCode CLA 		no flags Details
View All 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 CircleCode CLA 2011-02-24 02:29:11 EST 
When you have to choose a ref (say, for example, when you want to synchronise), only the last part of the ref is proposed.
In my case, I have the following branches:
- V1.0/dev
- V1.0/maint
- V2.0/dev
- V2.0/maint
The list proposed in the ref combobox is:
- dev
- dev
- maint
- maint
which is really confusing...
Comment 1 Stefan Lay CLA 2011-03-28 09:40:59 EDT 
I cannot reproduce that. Could you please describe in more detail which steps are needed to reproduce that? Which combobox is affected? Which version of EGit do you use?
Comment 2 CircleCode CLA 2011-03-28 10:20:12 EDT 
Created attachment 192005 [details]
list of remotes
Comment 3 CircleCode CLA 2011-03-28 10:20:57 EDT 
Created attachment 192006 [details]
team > synchronize wizard, showing the issue
Comment 4 CircleCode CLA 2011-03-28 10:21:26 EDT 
I use Egit 0.11.3, and I can reproduce the bug.

here are 2 attachments showing the issue.
Comment 5 Stefan Lay CLA 2011-03-29 05:27:01 EDT 
The bug was fixed in EGit 0.12 M1. You can try the nightly build to get the fix.

*** This bug has been marked as a duplicate of bug 327600 ***