Mirroring the sources cloned with repo (continued)

[Kasia]

Hi,

I am new to git and repo. I am trying do a set up like kanagesh
radhakrishnan's

http://groups.google.com/group/repo-discuss/browse_thread/thread/8f7fd6188aec1a0c/82b29766d18843af?lnk=gst&q=mirroring+the+sources+cloned+with+repo#82b29766d18843af

on my own local server.
I wish to have the server to work as a central repository for storing
projects from several developing teams. I also wish to use the server
as a way to share changes between developers. Teams need not
necessarily work on changes isolated to a project with a single git
repository but may need to work with modifications across several of
the .git repositories.

At the moment the developers are working in their own local repos.

I have a few questions about the setup and would also appreciate any
thoughts on the branaching strategy.

I have set up the local server

repo init –-mirror -u git://android.git.kernel.org/platform/manifest.git
-b cupcake
repo sync

I understand the default.xml in the server is transfered to the hosts
runing repo init [local server adress].
When a developer "clones" from the server like that is it posssible to
have him obtain a manifest directed
to the server or does every developer need to modify his default.xml
file to be able to sync from the local server?

How is a local_manifest.xml intended to be used?

As to the branching strategy and a recomended workflow...
Assuming the server will be used for several different local projects
-
these may need to be in sepearate branches. I asume these must be
created on the server by repo start localprojectA [project1 ..
projectx].

How do I set up the branches to be up to date with Android changes
when performing a repo sync on the server?
Should I keep the master branch on the server free of local changes
(just use it for repo sync) and let developers do merges from the
master branch to their development branches?

I then hope the developers to be able to do something like this:

repo init [path to local server] -b localprojectA
repo sync
cd [a project repository x]
<transfer current modifications from git repository in local repo to
x>
git commit -a
git push [the changes back to the local server for each project
containing modifications]

Then another developer should obtain any changes in the local
server by repo sync.

Best regards
Kasia