From dfdf577e98f6e9b13a3236767316863b3a995c01 Mon Sep 17 00:00:00 2001 From: Mike Frysinger Date: Thu, 30 Jan 2025 19:11:36 -0500 Subject: docs: smart-sync: split out & expand details The existing documentation on smart-sync behavior is a bit light on details, and out of date wrt what the code actually does. Start a dedicated document and fill it out more. Change-Id: I1a8a3ac6edf9291d72182ad55db865035d9b683e Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/450002 Commit-Queue: Mike Frysinger Tested-by: Mike Frysinger Reviewed-by: Josip Sokcevic --- docs/manifest-format.md | 21 +-------------------- 1 file changed, 1 insertion(+), 20 deletions(-) (limited to 'docs/manifest-format.md') diff --git a/docs/manifest-format.md b/docs/manifest-format.md index cfb80164..71fa04c5 100644 --- a/docs/manifest-format.md +++ b/docs/manifest-format.md @@ -231,26 +231,7 @@ At most one manifest-server may be specified. The url attribute is used to specify the URL of a manifest server, which is an XML RPC service. -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. 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 -of the form $TARGET_PRODUCT-$TARGET_BUILD_VARIANT, e.g. passion-userdebug. -If one of those variables or both are not present, the program will call -GetApprovedManifest without the target parameter and the manifest server -should choose a reasonable default target. - - GetManifest(tag) - -Return a manifest in which each project is pegged to the revision at -the specified tag. This is used by repo sync when the --smart-tag option -is given. +See the [smart sync documentation](./smart-sync.md) for more details. ### Element submanifest -- cgit v1.2.3-54-g00ecf