Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331292 - Cannot do push using a refspec with unspecified destination
Summary: Cannot do push using a refspec with unspecified destination
Status: CLOSED FIXED
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-28 19:15 EST by Vojislav Stojkovic CLA
Modified: 2013-09-27 12:02 EDT (History)
4 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 Vojislav Stojkovic CLA 2010-11-28 19:15:51 EST 
Build Identifier: 

With the current "Push Ref Specifications" dialog, I am forced to always specify the destination ref. This makes it impossible to do the equivalent of "git push origin :" or "git push origin HEAD".

Reproducible: Always

Steps to Reproduce:
Open the Push Wizard and advance to "Push Ref Specifications" step.
Comment 1 Remy Suen CLA 2010-11-28 19:42:49 EST 
You may also be interested in bug 312586.
Comment 2 Vojislav Stojkovic CLA 2010-11-28 22:29:29 EST 
(In reply to comment #1)
> You may also be interested in bug 312586.

Thanks, I've read that one already. To tell the truth, I was initially intimidated by the complexity of the dialog, but in the end it just made me learn more about refs and refspecs. Now I'm perfectly okay with having a complicated dialog (although simplifying it would be even better), as long as it allows me to do same things I could from CLI. Since it doesn't, I thought that filing a bug might be useful ;)
Comment 3 Matthias Sohn CLA 2011-03-11 18:50:38 EST 
Try "Push to upstream" which was added recently [1]. If that's what you miss close this bug.

[1] http://wiki.eclipse.org/EGit/User_Guide#Pushing_to_upstream