{"thread":{"id":"32142","subject":"[ANNOUNCE] namespace support in gitolite","startedAt":"2012-11-18T11:41:27Z","lastAt":"2012-11-18T11:41:27Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"203486","messageId":"CAMK1S_hGPb5nMs1-w9qtjwGnS4VrgfxG-yRP2b0p7Y=DRk=2Dw@mail.gmail.com","threadId":"32142","inReplyTo":null,"subject":"[ANNOUNCE] namespace support in gitolite","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2012-11-18T11:41:27Z","receivedAt":"2012-11-18T11:41:27Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Hello all,\n\nGitolite now supports namespaces on the server side (invisible\nto the client side of course).  See [1] for details.\n\nA simple way to describe it would be that all the repos in the\ntop row of the picture in the \"integration manager workflow\" at\n[2] are stored in one physical repo on the server, which saves a\nlot of disk space as well as network traffic for pushes to a\n\"new\" repo.\n\nThis is all on the server side.  On the client side they\ncontinue to look like separate repos, so nothing changes.\n\nIn addition, gitolite's 'upstream' trigger can be used to keep\nthe main repo in sync with the real upstream (somewhere on the\ninternet) if you wish.\n\nA bit more detail and a small example is at [3].\n\n[1]: http://sitaramc.github.com/gitolite/namespaces.html\n[2]: http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Integration-Manager-Workflow\n[3]: http://groups.google.com/group/gitolite/browse_thread/thread/5efcbfb5ff3ebe88\n\n-- \nSitaram\n"}]}