namespaces support in gitolite

[Sitaram Chamarty]

Hi all,

Gitolite now supports namespaces on the server side (invisible
to the client side of course). See [1] for details.

A simple way to describe it would be that all the repos in the
top row of the picture in the "integration manager workflow" at
[2] are stored in one physical repo on the server, which saves a
lot of disk space as well as network traffic for pushes to a
"new" repo.

This is all on the server side. On the client side they
continue to look like separate repos, so nothing changes.

In addition, gitolite's 'upstream' trigger can be used to keep
the main repo in sync with the real upstream (somewhere on the
internet) if you wish.

[1]: http://sitaramc.github.com/gitolite/namespaces.html
[2]: http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Integration-Manager-Workflow

----

An example setup follows; please ignore the rest of this email
if you're not (immediately) interested.

repo linux
R = @all
option upstream.url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
option upstream.nice = 120 # dont try to fetch more than once in 2 hours

repo CREATOR/copy/..*
C = @all
RW+ = CREATOR
R = @all
option namespace.pattern = %/copy/% is @1 in @2

Once the admin sets this up, a user alice can treat the repo
called 'alice/copy/linux' (which will be auto-created the first
time she references it) as her copy of the linux repo, to push
whatever she wants so that others can fetch it and work with it.

She also has the repo 'linux' available to fetch from; this is
the "blessed" repo in link [2] above.

Finally, the 'upstream' setting lets gitolite automatically
fetch the latest updates from k.o (with a minimum gap between
fetches of whatever duration you want, to be nice to k.o).

[Just to be complete, there are also some lines you need to add
to the file ~/.gitolite.rc but I'm going to ignore those here].

--
Sitaram