Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 364149 - Remote name is not correctly resolved in the Fetch wizard after adding a remote
Summary: Remote name is not correctly resolved in the Fetch wizard after adding a remote
Status: RESOLVED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Kevin Sawicki CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-18 08:35 EST by Manuel Doninger CLA
Modified: 2011-11-25 10:24 EST (History)
0 users

See Also:

Attachments
Screenshot with bug (5.87 KB, image/png)
2011-11-18 08:36 EST, Manuel Doninger 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 Manuel Doninger CLA 2011-11-18 08:35:22 EST 
Build Identifier: 1.2.0.201111171912

If you create a new remote in the Repository view, choose to configure Fetch, change the fetch url and then add a new refspec mapping with the Advanced dialog, the remote name is not correctly recognized. In my case it adds refs/remotes/org.eclipse.jgit.transport.RemoteConfig@443ad265/master as destination ref in the dialog (screenshot attached). Adding refspecs in the Configure Fetch wizard works without problems.

Reproducible: Always
Comment 1 Manuel Doninger CLA 2011-11-18 08:36:05 EST 
Created attachment 207215 [details]
Screenshot with bug
Comment 2 Kevin Sawicki CLA 2011-11-21 19:34:51 EST 
Proposed fix pushed to: http://egit.eclipse.org/r/#change,4660
Comment 3 Stefan Lay CLA 2011-11-25 10:24:46 EST 
Fixed with 40492cbfc11d4caa3b268d5bb141284d25f0a8d5