Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363469 - 'Push to Upstream' does not indicate to which remote it pushes
Summary: 'Push to Upstream' does not indicate to which remote it pushes
Status: CLOSED DUPLICATE of bug 441940
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 1.2   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-10 09:11 EST by Dani Megert CLA
Modified: 2022-02-18 14:12 EST (History)
5 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 Dani Megert CLA 2011-11-10 09:11:51 EST 
1.2.

I could not figure out a difference between 'Push' and 'Push to Upstream'. If they are the same then they should use the same label.
Comment 1 Remy Suen CLA 2011-11-11 09:23:16 EST 
(In reply to comment #0)
> I could not figure out a difference between 'Push' and 'Push to Upstream'.

'Team > Remote > Push...' with the ellipsis opens a wizard that lets you define what you want to push.

'Team > Push to Upstream', which has no ellipsis, is an "instant" action without a dialog and automatically pushes to upstream based on what you previously defined in the 'Team > Remote > Configure Push to Upstream...' dialog.
Comment 2 Dani Megert CLA 2011-11-14 03:20:48 EST 
(In reply to comment #1)
> (In reply to comment #0)
> > I could not figure out a difference between 'Push' and 'Push to Upstream'.
> 
> 'Team > Remote > Push...' with the ellipsis opens a wizard that lets you define
> what you want to push.
> 
> 'Team > Push to Upstream', which has no ellipsis, is an "instant" action
> without a dialog and automatically pushes to upstream based on what you
> previously defined in the 'Team > Remote > Configure Push to Upstream...'
> dialog.

Thanks, I already I knew that. I was asking for the difference between 'Push' and 'Push to Upstream'. Note the missing '...' ;-). Ah, and the 'Push' action is on nodes under Remotes > <something> push node
Comment 3 John Arthorne CLA 2012-12-13 14:36:45 EST 
I think this question was answered. When you select a single remote, there are "Configure Push..." and "Push" commands. The first one configures what the second one does... When you select an entire repository, there is Push to Upstream. I still find the word "Upstream" vague but I guess what this really means is "origin" as opposed to other remotes you might have.
Comment 4 Dani Megert CLA 2012-12-20 06:44:16 EST 
(In reply to comment #3)
> I still find the word "Upstream" vague but I guess what this
> really means is "origin" as opposed to other remotes you might have.

Well, almost. It means the remote of the checked out branch and that remote is not visible in the 'Git Repositories' view unless I look at the config file or configure the branch. So, I think it would make sense to rename this to
Push to 'remote name'
Fetch from 'remote name'

In most cases this would be:
Push to 'origin'
Fetch from 'origin'


And in the case of only one single remote, one could simply use 'Push' and 'Fetch'.
Comment 5 Rolf Theunissen CLA 2019-02-08 04:03:02 EST 
This bug is a duplicate of Bug 441940
Comment 6 Dani Megert CLA 2019-02-08 04:26:05 EST 
(In reply to Rolf Theunissen from comment #5)
> This bug is a duplicate of Bug 441940
Or the other way around ;-).
Comment 7 Thomas Wolf CLA 2022-02-18 14:12:46 EST 

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