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

Re: Re* [PATCH v2 1/2] refs: refs/worktree/* become per-worktree

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 11, 2015, 22:26 UTC
Message-ID
<xmqqlhdho417.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1439329355.5283.34.camel@twopensource.com>
David Turner <dturner@twopensource.com> writes:
> What does gitk do that's relevant here?

Ahh, my mistake. "gitk" spawned from "bisect visualize" is not even aware of the fact that it is showing the revision ranges delimited by the bisect references.

Previous: David TurnerNext: David Turner
Message 5 of 6 in “refs: refs/worktree/* become per-worktree”
  1. 1/2 refs: refs/worktree/* become per-worktreeDavid Turner, Aug 11, 2015
  2. 2/2 bisect: make bisection refs per-worktreeDavid Turner, Aug 11, 2015
  3. Re* [PATCH v2 1/2] refs: refs/worktree/* become per-worktreeJunio C Hamano, Aug 11, 2015
  4. David TurnerAug 11, 2015
  5. Junio C HamanoAug 11, 2015
  6. David TurnerAug 11, 2015

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.