superproject: support a new revision attribute.
Tested:
$ ./run_tests
Verified that a manifest that specified superproject revision would use
the specified revision, and superproject will use the default revision.
Note that this is a slight behavior change from earlier repo versions,
which would always use the branch name of the manifest itself. However,
the new behavior would be more consisitent with regular "project"
element and would allow superproject be used even if it is not enabled
for the particular manifest branch, so we have decided to make the
change as it would provide more flexibility and better matches what
other elements would do.
Bug: [google internal] b/187868160
Change-Id: I35255ee347aff6e65179f7879d52931f168b477e
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/317643
Tested-by: Xin Li
Reviewed-by: Raman Tenneti
Reviewed-by: Mike Frysinger
diff --git a/docs/manifest-format.md b/docs/manifest-format.md
index 854e5e1..ed297ae 100644
--- a/docs/manifest-format.md
+++ b/docs/manifest-format.md
@@ -103,8 +103,9 @@
-
-
+
+
+
@@ -432,6 +433,11 @@
Attribute `remote`: Name of a previously defined remote element.
If not supplied the remote given by the default element is used.
+Attribute `revision`: Name of the Git branch the manifest wants
+to track for this superproject. If not supplied the revision given
+by the remote element is used if applicable, else the default
+element is used.
+
### Element contactinfo
***
