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
This commit is contained in:
David Pursehouse 2016-04-13 17:55:34 +09:00
parent bdb866ea76
commit e868841782

View File

@ -175,7 +175,8 @@ The manifest server should implement the following RPC methods:
GetApprovedManifest(branch, target) GetApprovedManifest(branch, target)
Return a manifest in which each project is pegged to a known good revision 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 The target to use is defined by environment variables TARGET_PRODUCT
and TARGET_BUILD_VARIANT. These variables are used to create a string and TARGET_BUILD_VARIANT. These variables are used to create a string
@ -187,7 +188,8 @@ should choose a reasonable default target.
GetManifest(tag) GetManifest(tag)
Return a manifest in which each project is pegged to the revision at 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 Element project