On Sun, Aug 21, 2016 at 12:30:16PM +0100, Richard wrote: > On 21 August 2016 at 03:05, Josh Triplett <josh@xxxxxxxxxxxxxxxx> wrote: > > Unfortunately, I think at this point, GIT_NAMESPACE has to exclusively > > refer to the namespace for the remote end, to avoid breakage. Which > > means any automatic pervasive support for namespaces on the local side > > would need to use a different mechanism. (In addition to applying to > > ref enumeration, this would also need to apply to the local end of > > refspecs.) And this new mechanism would need to not affect the remote > > end, to allow remapping the local end while accessing an un-namespaced > > (or differently namespaced) remote. > > The problem for hooks is that it is implicitly inherited, > so it could work if upload-pack receive-pack and http-backend work > with GIT_NAMESPACE set, > but everything else that wants to use a namespace has to set > --namespace on the command-line. I'd like to see it work more automatically than that. Perhaps a separate environment variable to set the client-side namespace? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html