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

Re: [PATCHv5 2/4] Add infrastructure for ref namespaces

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 3, 2011, 23:22 UTC
Message-ID
<7vd3iua4bm.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1307136593-16306-3-git-send-email-jamey@minilop.net>
Jamey Sharp <jamey@minilop.net> writes:
Show 5 quoted lines
> Note that namespaces which include a / will expand to a hierarchy of
> namespaces; for example, GIT_NAMESPACE=foo/bar will store refs under
> refs/namespaces/foo/refs/namespaces/bar/.  This makes GIT_NAMESPACE
> behave hierarchically, and avoids ambiguity with namespaces such as
> foo/refs/heads.

I would have expected that this explanation would be improved after you having to answer my question on the list. Otherwise it was a wasted effort, for both me (asking) and you (answering).

Show 7 quoted lines
>
> This adds the infrastructure for ref namespaces: handling the
> GIT_NAMESPACE environment variable and --namespace option, and iterating
> over refs in a namespace.  Subsequent commits use this infrastructure to
> implement the user-visible support for ref namespaces.
>
> Commit by Josh Triplett and Jamey Sharp.
Also please drop that "Commit by ...".  We can read Sign-off.
Previous: Jamey SharpNext: Josh Triplett
Message 4 of 9 in “[PATCHv5 0/4] Support ref namespaces”
  1. Jamey SharpJun 3, 2011
  2. 1/4 Fix prefix handling in ref iteration functionsJamey Sharp, Jun 3, 2011
  3. 2/4 Add infrastructure for ref namespacesJamey Sharp, Jun 3, 2011
  4. Junio C HamanoJun 3, 2011
  5. Josh TriplettJun 3, 2011
  6. 3/4 Support ref namespaces for remote repositories via upload-pack and receive-packJamey Sharp, Jun 3, 2011
  7. 4/4 Add documentation for ref namespacesJamey Sharp, Jun 3, 2011
  8. Junio C HamanoJun 3, 2011
  9. Josh TriplettJun 3, 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.