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

Re: proposal for how to share other refs as part of refs/tracking/*

From
Marc Branchaud <marcnarc@xiplink.com>
Date
Jun 13, 2017, 15:55 UTC
Message-ID
<010f8a1b-cab3-fada-0f38-1f0726283f5e@xiplink.com>
In-Reply-To
<48064f67-6d88-8c14-853e-fd9214d26647@xiplink.com>
On 2017-06-13 10:41 AM, Marc Branchaud wrote:
> 
> So I like your refs/tracking proposal, and hope that it aims for 
> mirroring a remote's refs, to eventually replace refs/remotes entirely.
To be extra-clear:

I think a refs/tracking hierarchy that starts with notes and maybe some other bits is a good first step.

I *hope* such a first step can eventually mirror all of a remote's refs, including heads and tags.

I in no way think that this effort should begin by tackling heads and tags.
		M.
Previous: Marc BranchaudNext: Jacob Keller
Message 3 of 4 in “proposal for how to share other refs as part of refs/tracking/*”
  1. Jacob KellerJun 12, 2017
  2. Marc BranchaudJun 13, 2017
  3. Marc BranchaudJun 13, 2017
  4. Jacob KellerJun 14, 2017

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.