Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337853 - fetch ignoring remote name and creating fetched brances as "choose_remote_name/master"
Summary: fetch ignoring remote name and creating fetched brances as "choose_remote_nam...
Status: ASSIGNED
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: 0.11   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Stefan Lay CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-22 11:00 EST by cam_neely CLA
Modified: 2011-05-09 15:03 EDT (History)
2 users (show)

See Also:


Attachments
screenshot of egit repository view showing the issue (2.93 KB, image/png)
2011-02-22 11:00 EST, cam_neely CLA
no flags Details
Remote Setup (72.06 KB, image/png)
2011-05-09 15:03 EDT, Miles Parker CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description cam_neely CLA 2011-02-22 11:00:00 EST
Created attachment 189508 [details]
screenshot of egit repository view showing the issue

I had already defined a remote called "origin", and configured fetching/pushing months ago using EGit.  

When i recently performed a fetch from our 'central' repository at work, I realized that the fetch did not fetch the master branch into origin/master, but rather choose_remote_name/master.

I've noticed this on a windows xp at work and unbuntu linux at home.

I'm not sure the exact point where this started because I only recently performed a fetch for the first time in a while.

I am using the nightly builds.

see attached screenshot for the visuals...
Comment 1 Stefan Lay CLA 2011-03-28 10:09:59 EDT
It seems that your remote configuration was lost in between and the Fetch wizard did not know which remote name it should use. In this case it inserts a placeholder "choose_remote_name". 

If you still have the repo in that state, could you please make a screenshot of the "Remotes" node in the Git Repositories View or attach the content of the configuration of the repository (from the repository node in the Git Repositories View click "Open Properites View")?
Comment 2 Miles Parker CLA 2011-05-09 15:03:43 EDT
Created attachment 195128 [details]
Remote Setup

I'm having the same issue. Here's what I'm seeing. One bit of info, in this case I'd just imported my workspace into a new Applicaiton instance (M6 -> M7, but I've seen the issue at least since M6). Also, I use Buckminster to import projects and I've seen some odd interactions here.

BTW, how to safely fix when this has happened? Do we just change the fetch refspec?