git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Adding more namespace support to git

From
Josh Triplett <josh@joshtriplett.org>
Date
Aug 21, 2016, 14:07 UTC
Message-ID
<20160821140710.qpbm37nhhvbkmxgz@x>
In-Reply-To
<CAB2VqoZdj1rhdt-4gUhXTAMQjJTOqCuwXiO6yfB2Fzyy_qSWHg@mail.gmail.com>
On Sun, Aug 21, 2016 at 12:30:16PM +0100, Richard wrote:
Show 15 quoted lines
> On 21 August 2016 at 03:05, Josh Triplett <josh@joshtriplett.org> 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?

Previous: RichardNext: Jeff King
Message 4 of 7 in “Adding more namespace support to git”
  1. RichardAug 20, 2016
  2. Josh TriplettAug 21, 2016
  3. RichardAug 21, 2016
  4. Josh TriplettAug 21, 2016
  5. Jeff KingAug 24, 2016
  6. Josh TriplettAug 22, 2016
  7. RichardAug 22, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.