Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 315145

Summary:	Usability: pushing changes from cloned repo requires (unnecessary) push target specification
Product:	[Technology] EGit	Reporter:	Kay Huber <quorg.xtn>
Component:	Core	Assignee:	Project Inbox <egit.core-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	mathias.kinzler
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows Vista
Whiteboard:

Description Kay Huber

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

2010-06-01 02:24:23 EDT

Already fixed on Bug 314573.

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