FetchGerritChangePage: also try to determine the patch set number
commitde432f48f6b167604ad8c84045865757e1219a46
authorThomas Wolf <thomas.wolf@paranor.ch>
Tue, 20 Jun 2017 11:54:05 +0000 (20 13:54 +0200)
committerThomas Wolf <thomas.wolf@paranor.ch>
Wed, 28 Jun 2017 07:24:48 +0000 (28 09:24 +0200)
tree3be33d176d33a4e14b167fe399e78c8fdfd7159d
parent5389fe06703847fad6c39702d4fe571090a160d4
FetchGerritChangePage: also try to determine the patch set number

If we can determine a patch set number, try to build and insert a
valid change ref in the Change field instead of just the change
number. If the user knows it's valid, he doesn't have to wait for
the background ls-remote to finish and can continue right away. If
the Gerrit server does not actually have a change for the ref, the
fetch will then fail, of course.

Bug: 518492
Change-Id: Iddf58173a4272e5d8ef642827372c630184c5370
Signed-off-by: Thomas Wolf <thomas.wolf@paranor.ch>
org.eclipse.egit.ui.test/src/org/eclipse/egit/ui/internal/fetch/FetchGerritChangeTest.java
org.eclipse.egit.ui/src/org/eclipse/egit/ui/internal/fetch/FetchGerritChangePage.java