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

Re: [RFC PATCH 1/1] Teach remote add the --prefix-tags option

From
Wink Saville <wink@saville.com>
Date
Oct 15, 2019, 17:56 UTC
Message-ID
<CAKk8isq0W86ONoEMxh7kiik75qeOxvznh2j1-91GEehZQDzRrA@mail.gmail.com>
In-Reply-To
<xmqq4l0ad7vn.fsf@gitster-ct.c.googlers.com>
Show 16 quoted lines
> In short, if you truly want to see "separate hierarchy per remote",
> you should consider how you can reliably implement an equivalent of
> "git branch --list --remote"; a design that does not allow it is a
> failure.
>
> A better solution with longer lifetime would probably be to use
>
>         refs/remotes/$remoteName/{heads,tags,...}/
>
> when core.useTotallySeparateRemote configuration exists (and
> eventually at Git 3.0 make the layout the default).  It would
> involve changes in the refname look-up rules, but it would not have
> to pollute refs/ namespace like the refs/remoteTags/ half-ground
> design, which would require us to add refs/remoteNotes/ and friends,
> who knows how many more we would end up having to support if we go
> that route.

I've used submodules a little bit and in some sense it seems to already implement core.useTotallySeparateRemote. So from my perspective trying to make this change significantly different this isn't worth the effort and I'm not sure I have the expertise to do it well.

Is there a roadmap and or timeline for Git 3.0?
Previous: Junio C HamanoNext: Jacob Keller
Message 4 of 6 in “Teach remote add a --prefix-tags option”
  1. 0/1 Teach remote add a --prefix-tags optionWink Saville, Oct 14, 2019
  2. 1/1 Teach remote add the --prefix-tags optionWink Saville, Oct 14, 2019
  3. Junio C HamanoOct 15, 2019
  4. Wink SavilleOct 15, 2019
  5. Jacob KellerOct 15, 2019
  6. Jacob KellerOct 16, 2019

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.