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

Re: [RFC PATCH] proposal for refs/tracking/* hierarchy

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 26, 2017, 19:28 UTC
Message-ID
<xmqqvani4kgs.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<aa8a7ff6-2068-645d-061e-3142760a4b2a@xiplink.com>
Marc Branchaud <marcnarc@xiplink.com> writes:
Show 7 quoted lines
> OTOH, we shouldn't need to do any conflict resolution on these
> "tracking" refs:  The remote side should update the refs
> properly. Nobody should make local changes to these refs.
>
> I guess I'm advocating that git should only allow "tracking" refs to
> be updated by a fetch, or a successful push of a local, non-"tracking"
> ref.

I do not think anybody is imagining new things to happen inside refs/tracking other than by fetching, just like refs/remotes/ refs behave like so.

What I was discussing was mostly the step next to the introduction of tracking/. Some things are useful merely by existing (e.g. tags you got from remote, as long as you can easily refer to them, are useful to you). Some other things are cumbersome to use until you manage to consolidate your views with theirs in order to make collective progress, and they require merging (e.g. notes).

Previous: Marc Branchaud
Message 6 of 6 in “proposal for refs/tracking/* hierarchy”
  1. proposal for refs/tracking/* hierarchyJacob Keller, Jun 23, 2017
  2. Jacob KellerJun 23, 2017
  3. Junio C HamanoJun 23, 2017
  4. Jacob KellerJun 23, 2017
  5. Marc BranchaudJun 26, 2017
  6. Junio C HamanoJun 26, 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.