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

Bug 340308

Summary:	Pull should work with multiple repositories
Product:	[Technology] EGit	Reporter:	Robin Stocker <robin>
Component:	Core	Assignee:	Project Inbox <egit.core-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mathias.kinzler
Version:	unspecified
Target Milestone:	0.12-M2
Hardware:	All
OS:	All
Whiteboard:

Description Robin Stocker

2011-03-17 09:14:00 EDT

Build Identifier: 

When having multiple projects (each corresponding to a different repository) and needing to regularly keep up to date with changes, EGit provides no easy way to deal with this.

The only way at the moment is to select a single project and pull, and repeat that for every project. When the number of projects is two, this is okay, but for more than a couple of projects it's simply infeasible.

Bug 326635 would improve this, but the synchronize view has too many problems at the moment to be usable.

Reproducible: Always

Comment 1 Robin Stocker

2011-03-17 09:24:29 EDT

To give a bit of context why this is needed: There are products which consist of many more or less independent modules. The question arises how to organize them in Git repositories.

One solution is to have one repository per module, which separates the histories nicely and allows to only have the required modules cloned.

Another one is to create one big repository which contains all the modules as subdirectories. This has the disadvantage that merge/rebase is often necessary in daily work even when the development is done on separate modules.

With the current state of EGit, only the second solution is feasible.

Comment 2 Mathias Kinzler

2011-03-24 13:01:18 EDT

Change: http://egit.eclipse.org/r/#change,2755
Merged as 4197370f09f23e4930ac80a045097cbd4946ea8e