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

Re: Painless namespaces design

From
Shawn Pearce <spearce@spearce.org>
Date
Jun 15, 2011, 14:00 UTC
Message-ID
<BANLkTiktjki43wCX5d2SV+tKjp_fqmGznw@mail.gmail.com>
In-Reply-To
<4DF894FD.9040808@gmail.com>
2011/6/15 Jiang Xin <worldhello.net@gmail.com>:
> I like the idea of new namespaces feature from Josh Triplett, Jamey Sharp and others.
> I think it is better to pass namespace through remote.remote-name.namespace variables,
> not through GIT_NAMESPACE environment.
...
Show 8 quoted lines
>    [remote "origin"]
>        namespace = foo
>        fetch = +refs/heads/*:refs/remotes/origin/*
>        url = ssh://Host1/path/to/project.git
>
> When UserA runs `git fetch`, it's just like
>
>    git fetch origin refs/namespaces/foo/refs/heads/*:refs/remotes/origin/*

This is less than ideal. Part of the rationale for the GIT_NAMESPACE environment variable is to allow the server to restrict the namespace and only show that specific slice of the repository's refs to the client. It allows a server administrator to put several logical repositories into a single repository, and have clients be oblivious to this fact.

-- 
Shawn.
Previous: Jiang Xin
Message 10 of 10 in “[PATCHv8 0/4] Support ref namespaces”
  1. Jamey SharpJun 7, 2011
  2. 1/4 Fix prefix handling in ref iteration functionsJamey Sharp, Jun 7, 2011
  3. Junio C HamanoJun 8, 2011
  4. Josh TriplettJun 8, 2011
  5. 2/4 Add infrastructure for ref namespacesJamey Sharp, Jun 7, 2011
  6. 3/4 Support ref namespaces for remote repositories via upload-pack and receive-packJamey Sharp, Jun 7, 2011
  7. 4/4 Add documentation for ref namespacesJamey Sharp, Jun 7, 2011
  8. Marc BranchaudJun 8, 2011
  9. Painless namespaces designJiang Xin, Jun 15, 2011
  10. Shawn PearceJun 15, 2011

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.