Re: Access different NAMESPACE of remote repo from client side

2013-11-16 Thread Sitaram Chamarty
On 11/16/2013 01:30 PM, Jiang Xin wrote: > 2013/11/15 Sitaram Chamarty : >> On 11/15/2013 07:55 PM, Sitaram Chamarty wrote: [snip] >> I should add that the Gitolite model is: the user doesn't need to know >> about namespaces, because namespaces are just things that the server >> admin is setting

Re: Access different NAMESPACE of remote repo from client side

2013-11-16 Thread Jiang Xin
2013/11/15 Sitaram Chamarty : > On 11/15/2013 07:55 PM, Sitaram Chamarty wrote: >> On 11/15/2013 01:49 PM, Jiang Xin wrote: >>> Just like solution 2, these settings won't work without a patched >>> git-shell or gitolite. >> >> Gitolite has a namespaces branch that handles namespaces as described in

Re: Access different NAMESPACE of remote repo from client side

2013-11-15 Thread Sitaram Chamarty
On 11/15/2013 07:55 PM, Sitaram Chamarty wrote: > On 11/15/2013 01:49 PM, Jiang Xin wrote: >> GIT_NAMESPACE is designed to be used mainly on the server side, that >> the server can serve multiple git repositories while share one single >> repository storage using different GIT_NAMESPACE settings. >

Re: Access different NAMESPACE of remote repo from client side

2013-11-15 Thread Sitaram Chamarty
On 11/15/2013 01:49 PM, Jiang Xin wrote: > GIT_NAMESPACE is designed to be used mainly on the server side, that > the server can serve multiple git repositories while share one single > repository storage using different GIT_NAMESPACE settings. > > Since we know that one remote repository hosts mu

Access different NAMESPACE of remote repo from client side

2013-11-15 Thread Jiang Xin
GIT_NAMESPACE is designed to be used mainly on the server side, that the server can serve multiple git repositories while share one single repository storage using different GIT_NAMESPACE settings. Since we know that one remote repository hosts multiple namespaces, can we handle different namespac