4 Commits

Author	SHA1	Message	Date
Shawn O. Pearce	70939e2f73	Add <add-remote to-project="..."> to inject additional remotes ... 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>	2008-11-06 11:23:08 -08:00
Shawn O. Pearce	ae6e0949d1	Add <remote project-name="..."> attribute within projects ... 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>	2008-11-06 11:23:06 -08:00
Shawn O. Pearce	70cd4ab270	Add some short documentation about the local manifest ... Signed-off-by: Shawn O. Pearce <sop@google.com>	2008-11-06 08:48:44 -08:00
Shawn O. Pearce	3e5481999d	Add a basic outline of the repo manifest file format ... Signed-off-by: Shawn O. Pearce <sop@google.com>	2008-11-04 11:19:36 -08:00