Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315145 - Usability: pushing changes from cloned repo requires (unnecessary) push target specification
Summary: Usability: pushing changes from cloned repo requires (unnecessary) push targe...
Status: CLOSED DUPLICATE of bug 314573
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 16:31 EDT by Kay Huber CLA
Modified: 2010-06-01 02:24 EDT (History)
1 user (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 Kay Huber CLA 2010-05-31 16:31:30 EDT 
Referring to latest nightlies of both EGit (0.8.0.201005300830) and JGit (0.8.0.201005300828).

When I clone a repository, commit some changes and then press "Push..." to push my changes back to the original repo, I am presented the "Destination git repository" dialog where I have to specify the push target repository. Why?

I understand it may make sense to push to other repositories than the originally cloned one, but to me it seems like it is more often the clone origin to be pushed to, so it would be good to at least have the choice between "existing repos" and a new one.
Comment 1 Mathias Kinzler CLA 2010-06-01 02:24:23 EDT 
Already fixed on Bug 314573.

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