RepoCommand: Skip RemoteReader when encountering a full SHA-1
There is no point in calling back to the RemoteReader to resolve a 40-digit hex SHA-1 to itself. We already skip that call when not ignoring remote failures; skip it when ignoring remote failures, too. This should simplify RemoteReader implementations. Reported-by: Han-Wen Nienhuys <hanwen@google.com> Change-Id: I7566968ed1f39b1ad73574fa903faf3ee308eb87
This commit is contained in:
parent
c213f0a4cd
commit
04b8168beb
|
@ -534,8 +534,7 @@ public RevCommit call() throws GitAPIException {
|
|||
String path = proj.getPath();
|
||||
String nameUri = proj.getName();
|
||||
ObjectId objectId;
|
||||
if (ObjectId.isId(proj.getRevision())
|
||||
&& !ignoreRemoteFailures) {
|
||||
if (ObjectId.isId(proj.getRevision())) {
|
||||
objectId = ObjectId.fromString(proj.getRevision());
|
||||
} else {
|
||||
objectId = callback.sha1(nameUri, proj.getRevision());
|
||||
|
|
Loading…
Reference in New Issue