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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 2, 2011, 22:44 UTC
Message-ID
<7vfwnrdfam.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1306887870-3875-2-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.

Sorry, but I fail to see what problem you are trying to solve here. I am not suggesting that it would be better to do things in a way different from what your patch does, but what problem will you have if you stored the branch head for baz in refs/namespaces/foo/bar/refs/heads/baz given the namespace foo/bar, and how does it solve that problem to store it instead at refs/namespaces/foo/refs/namespaces/bar/refs/heads/baz?

> +int for_each_namespaced_ref(each_ref_fn fn, void *cb_data)

Just a naming and interface preference, but I would have called this for-each-ref-in-namespace, perhaps giving the namespace as a parameter.

Previous: Jamey SharpNext: Josh Triplett
Message 3 of 20 in “[PATCHv4 1/4] Refactor for_each_ref variants to use for_each_ref_in and avoid magic numbers”
  1. Jamey SharpJun 1, 2011
  2. 2/4 Add infrastructure for ref namespacesJamey Sharp, Jun 1, 2011
  3. Junio C HamanoJun 2, 2011
  4. Josh TriplettJun 2, 2011
  5. Junio C HamanoJun 3, 2011
  6. Josh TriplettJun 3, 2011
  7. Jakub NarebskiJun 3, 2011
  8. Josh TriplettJun 3, 2011
  9. Jakub NarebskiJun 8, 2011
  10. Josh TriplettJun 9, 2011
  11. Jakub NarebskiJun 9, 2011
  12. 3/4 Support ref namespaces for remote repositories via upload-pack and receive-packJamey Sharp, Jun 1, 2011
  13. Junio C HamanoJun 2, 2011
  14. josh@joshtriplett.orgJun 3, 2011
  15. Junio C HamanoJun 3, 2011
  16. 4/4 Add documentation for ref namespacesJamey Sharp, Jun 1, 2011
  17. Junio C HamanoJun 2, 2011
  18. Josh TriplettJun 2, 2011
  19. Junio C HamanoJun 2, 2011
  20. Jakub NarebskiJun 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.