From e868841782314e431134c24c350f5a353306fa7d Mon Sep 17 00:00:00 2001 From: David Pursehouse Date: Wed, 13 Apr 2016 17:55:34 +0900 Subject: [PATCH] Improve documentation of manifest server RPC methods Mention that the RPC endpoints are used when running repo sync with the --smart-sync and --smart-tag options Change-Id: I4b0b82e8b714fe923a5b325a6135f0128bf636ff --- docs/manifest-format.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/manifest-format.txt b/docs/manifest-format.txt index 140a782f..8fd9137c 100644 --- a/docs/manifest-format.txt +++ b/docs/manifest-format.txt @@ -175,7 +175,8 @@ The manifest server should implement the following RPC methods: GetApprovedManifest(branch, target) Return a manifest in which each project is pegged to a known good revision -for the current branch and target. +for the current branch and target. This is used by repo sync when the +--smart-sync option is given. The target to use is defined by environment variables TARGET_PRODUCT and TARGET_BUILD_VARIANT. These variables are used to create a string @@ -187,7 +188,8 @@ should choose a reasonable default target. GetManifest(tag) Return a manifest in which each project is pegged to the revision at -the specified tag. +the specified tag. This is used by repo sync when the --smart-tag option +is given. Element project