diff options
| author | Shawn O. Pearce <sop@google.com> | 2009-05-19 13:00:29 -0700 |
|---|---|---|
| committer | Shawn O. Pearce <sop@google.com> | 2009-05-19 13:01:52 -0700 |
| commit | 242b52690d327a77e47140509085f406155c5722 (patch) | |
| tree | 92b58b51e6f0b38bea6cc98a0c67604c5d08b7f1 /docs | |
| parent | 4cc70ce501321733a1b389e685e964d34b3b4cf5 (diff) | |
| download | git-repo-242b52690d327a77e47140509085f406155c5722.tar.gz | |
Remove support for the extra <remote> definitions in manifests
These aren't that widely used, and actually make it difficult for
users to fully mirror a forest of repositories, and then permit
someone else to clone off that forest, rather then the original
upstream servers.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/manifest-format.txt | 39 |
1 files changed, 2 insertions, 37 deletions
diff --git a/docs/manifest-format.txt b/docs/manifest-format.txt index d8db21de..da0e69ff 100644 --- a/docs/manifest-format.txt +++ b/docs/manifest-format.txt | |||
| @@ -23,32 +23,23 @@ following DTD: | |||
| 23 | <!ELEMENT manifest (remote*, | 23 | <!ELEMENT manifest (remote*, |
| 24 | default?, | 24 | default?, |
| 25 | remove-project*, | 25 | remove-project*, |
| 26 | project*, | 26 | project*)> |
| 27 | add-remote*)> | ||
| 28 | 27 | ||
| 29 | <!ELEMENT remote (EMPTY)> | 28 | <!ELEMENT remote (EMPTY)> |
| 30 | <!ATTLIST remote name ID #REQUIRED> | 29 | <!ATTLIST remote name ID #REQUIRED> |
| 31 | <!ATTLIST remote fetch CDATA #REQUIRED> | 30 | <!ATTLIST remote fetch CDATA #REQUIRED> |
| 32 | <!ATTLIST remote review CDATA #IMPLIED> | 31 | <!ATTLIST remote review CDATA #IMPLIED> |
| 33 | <!ATTLIST remote project-name CDATA #IMPLIED> | ||
| 34 | 32 | ||
| 35 | <!ELEMENT default (EMPTY)> | 33 | <!ELEMENT default (EMPTY)> |
| 36 | <!ATTLIST default remote IDREF #IMPLIED> | 34 | <!ATTLIST default remote IDREF #IMPLIED> |
| 37 | <!ATTLIST default revision CDATA #IMPLIED> | 35 | <!ATTLIST default revision CDATA #IMPLIED> |
| 38 | 36 | ||
| 39 | <!ELEMENT project (remote*)> | 37 | <!ELEMENT project (EMPTY)> |
| 40 | <!ATTLIST project name CDATA #REQUIRED> | 38 | <!ATTLIST project name CDATA #REQUIRED> |
| 41 | <!ATTLIST project path CDATA #IMPLIED> | 39 | <!ATTLIST project path CDATA #IMPLIED> |
| 42 | <!ATTLIST project remote IDREF #IMPLIED> | 40 | <!ATTLIST project remote IDREF #IMPLIED> |
| 43 | <!ATTLIST project revision CDATA #IMPLIED> | 41 | <!ATTLIST project revision CDATA #IMPLIED> |
| 44 | 42 | ||
| 45 | <!ELEMENT add-remote (EMPTY)> | ||
| 46 | <!ATTLIST add-remote to-project ID #REQUIRED> | ||
| 47 | <!ATTLIST add-remote name ID #REQUIRED> | ||
| 48 | <!ATTLIST add-remote fetch CDATA #REQUIRED> | ||
| 49 | <!ATTLIST add-remote review CDATA #IMPLIED> | ||
| 50 | <!ATTLIST add-remote project-name CDATA #IMPLIED> | ||
| 51 | |||
| 52 | <!ELEMENT remove-project (EMPTY)> | 43 | <!ELEMENT remove-project (EMPTY)> |
| 53 | <!ATTLIST remove-project name CDATA #REQUIRED> | 44 | <!ATTLIST remove-project name CDATA #REQUIRED> |
| 54 | ]> | 45 | ]> |
| @@ -82,25 +73,6 @@ Attribute `review`: Hostname of the Gerrit server where reviews | |||
| 82 | are uploaded to by `repo upload`. This attribute is optional; | 73 | are uploaded to by `repo upload`. This attribute is optional; |
| 83 | if not specified then `repo upload` will not function. | 74 | if not specified then `repo upload` will not function. |
| 84 | 75 | ||
| 85 | Attribute `project-name`: Specifies the name of this project used | ||
| 86 | by the review server given in the review attribute of this element. | ||
| 87 | Only permitted when the remote element is nested inside of a project | ||
| 88 | element (see below). If not given, defaults to the name supplied | ||
| 89 | in the project's name attribute. | ||
| 90 | |||
| 91 | Element add-remote | ||
| 92 | ------------------ | ||
| 93 | |||
| 94 | Adds a remote to an existing project, whose name is given by the | ||
| 95 | to-project attribute. This is functionally equivalent to nesting | ||
| 96 | a remote element under the project, but has the advantage that it | ||
| 97 | can be specified in the uesr's `local_manifest.xml` to add a remote | ||
| 98 | to a project declared by the normal manifest. | ||
| 99 | |||
| 100 | The element can be used to add a fork of an existing project that | ||
| 101 | the user needs to work with. | ||
| 102 | |||
| 103 | |||
| 104 | Element default | 76 | Element default |
| 105 | --------------- | 77 | --------------- |
| 106 | 78 | ||
| @@ -152,13 +124,6 @@ Tags and/or explicit SHA-1s should work in theory, but have not | |||
| 152 | been extensively tested. If not supplied the revision given by | 124 | been extensively tested. If not supplied the revision given by |
| 153 | the default element is used. | 125 | the default element is used. |
| 154 | 126 | ||
| 155 | Child element `remote`: Described like the top-level remote element, | ||
| 156 | but adds an additional remote to only this project. These additional | ||
| 157 | remotes are fetched from first on the initial `repo sync`, causing | ||
| 158 | the majority of the project's object database to be obtained through | ||
| 159 | these additional remotes. | ||
| 160 | |||
| 161 | |||
| 162 | Element remove-project | 127 | Element remove-project |
| 163 | ---------------------- | 128 | ---------------------- |
| 164 | 129 | ||
