tools/git-repo.git/docs, branch v1.6.8Mirror of gerrit.googlesource.com/git-repohttps://git.enea.com/cgit/tools/git-repo.git/atom?h=v1.6.82009-05-19T20:01:52+00:00Remove support for the extra <remote> definitions in manifests2009-05-19T20:01:52+00:00Shawn O. Pearcesop@google.com2009-05-19T20:00:29+00:00urn:sha1:242b52690d327a77e47140509085f406155c5722
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>
Correct note about local_manifest.xml capabilities2009-04-18T18:25:58+00:00Shawn O. Pearcesop@google.com2009-04-18T18:25:58+00:00urn:sha1:a490f03dc23792a86bbe5b2b8c89b32f39774c80
With the <remove-project> element we can remove projects, and
fully replace them with a different definition. So this note
is out of date.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add a 'repo manifest' command whose help is the manifest file format2009-03-04T22:26:50+00:00Shawn O. Pearcesop@google.com2009-03-04T22:26:50+00:00urn:sha1:43c3d9ea17f1436a6b3b2e7e7827da6f48a21da9
This should make it easier for users to discover the file format
on their own, and read about it.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Support <remove-project name="X"> in manifest to remove/replace X2008-11-20T19:54:46+00:00Shawn O. Pearcesop@google.com2008-11-20T19:42:22+00:00urn:sha1:03eaf07ec6aa7e99a0444ac1ec708b2a5f7cbbf5
The manifest files now permit removing a project so the user can
either keep it out of their client, or replace it with a different
project using an entirely different configuration.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add <add-remote to-project="..."> to inject additional remotes2008-11-06T19:23:08+00:00Shawn O. Pearcesop@google.com2008-11-06T19:07:14+00:00urn:sha1:70939e2f73bf118c89cf4af4988dba807c50a0ce
This way users can add forks they know about to an existing project
that was already declared in the primary manifest. This is mostly
useful with the Linux kernel project, where multiple forks is quite
common for the main upstream tree (e.g. Linus' tree), a platform
architecture tree (e.g. ARM) and a device specific tree (e.g. the
msm7k tree used by Android).
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add <remote project-name="..."> attribute within projects2008-11-06T19:23:06+00:00Shawn O. Pearcesop@google.com2008-11-06T18:25:35+00:00urn:sha1:ae6e0949d187c35d79dbc0b21788fdbb2c65bf78
By setting a project-name on a remote nested within a project forks
of a project like the Linux kernel can be easily handled by fetching
all relevant forks into the same client side project under different
remote names. Developers can create branches off different remotes
using `git checkout --track -b $myname $remote/$branch` and later
`repo upload` automatically redirects to the proper fork project
in the code review server.
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add some short documentation about the local manifest2008-11-06T16:48:44+00:00Shawn O. Pearcesop@google.com2008-11-06T16:48:44+00:00urn:sha1:70cd4ab2708eaae7d96d7e8b0a3f88850c163543
Signed-off-by: Shawn O. Pearce <sop@google.com>
Add a basic outline of the repo manifest file format2008-11-04T19:19:36+00:00Shawn O. Pearcesop@google.com2008-11-04T19:19:36+00:00urn:sha1:3e5481999d5f853e19ee5caaaaa968fc4b5176ab
Signed-off-by: Shawn O. Pearce <sop@google.com>