From accc95dc6b168ea323a18893ed6d00e64b81e343 Mon Sep 17 00:00:00 2001 From: Elliott Hughes Date: Fri, 22 Jun 2018 13:12:19 -0700 Subject: [PATCH] adb: fix obsolete documentation. Bug: http://b/110564383 Obsolete adb document, inconsistent with current implementation Test: N/A Change-Id: If12ba8546991ee6f2a89ca0ff8036b598742dc11 --- adb/OVERVIEW.TXT | 3 --- adb/SERVICES.TXT | 4 ---- 2 files changed, 7 deletions(-) diff --git a/adb/OVERVIEW.TXT b/adb/OVERVIEW.TXT index 29a699254..f0b184c99 100644 --- a/adb/OVERVIEW.TXT +++ b/adb/OVERVIEW.TXT @@ -103,9 +103,6 @@ II. Protocol details: 4-byte hex length, followed by a string giving the reason for failure. - 3. As a special exception, for 'host:version', a 4-byte - hex string corresponding to the server's internal version number - Note that the connection is still alive after an OKAY, which allows the client to make other requests. But in certain cases, an OKAY will even change the state of the connection. diff --git a/adb/SERVICES.TXT b/adb/SERVICES.TXT index 30c21f70e..3e18a54e7 100644 --- a/adb/SERVICES.TXT +++ b/adb/SERVICES.TXT @@ -7,10 +7,6 @@ HOST SERVICES: host:version Ask the ADB server for its internal version number. - As a special exception, the server will respond with a 4-byte - hex string corresponding to its internal version number, without - any OKAY or FAIL. - host:kill Ask the ADB server to quit immediately. This is used when the ADB client detects that an obsolete server is running after an