Community
Participate
Working Groups
Steps: 1. Select multiple repositories 2. Open context menu Push always shows as disabled for me.
(In reply to comment #0) > Push always shows as disabled for me. I presume you mean 'Pull', which is what I see and what you wrote in the summary, correct?
Thanks for pointing that out. Yes, I meant "Pull".
'Fetch from Upstream' is also not available, see bug 349560.
(In reply to comment #2) > Thanks for pointing that out. Yes, I meant "Pull". A change set has been pushed to Gerrit for review. http://egit.eclipse.org/r/#change,4303 (In reply to comment #3) > 'Fetch from Upstream' is also not available, see bug 349560. Dani, let's leave that to bug 349560.
Jens has merged my change set to master. http://egit.eclipse.org/w/?p=egit.git;a=commit;h=e7cf32fbf68eeff56b31fba5cfd73f4b87a6863e Setting target milestone to 1.1 (because we don't seem to have a 1.2).
Forgot to mark this as RESOLVED/FIXED yesterday.
(In reply to comment #5) > Setting target milestone to 1.1 (because we don't seem to have a 1.2). Verified with EGit 1.2.0.201109300615 on Windows XP.
Nice! Can I now also get bug 349560 (Fetch from Upstream). Shouldn't be too hard now ;-)
Something seems to be fishy (might be related to this fix): I now get this on each start: !ENTRY org.eclipse.ui.workbench 2 0 2011-10-04 12:42:51.660 !MESSAGE A handler conflict occurred. This may disable some commands. !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2011-10-04 12:42:51.660 !MESSAGE Conflict for 'org.eclipse.egit.ui.team.Pull': HandlerActivation(commandId=org.eclipse.egit.ui.team.Pull, handler=org.eclipse.egit.ui.internal.repository.tree.command.PullCommand, expression=org.eclipse.core.internal.expressions.IterateExpression@71c93206,sourcePriority=1073741824) HandlerActivation(commandId=org.eclipse.egit.ui.team.Pull, handler=org.eclipse.egit.ui.internal.actions.PullFromUpstreamActionHandler, expression=org.eclipse.core.internal.expressions.IterateExpression@338cc288,sourcePriority=1073741824)
(In reply to comment #9) > Something seems to be fishy (might be related to this fix) File bug 359819.