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

Re: [PATCH v2] notes: handle multiple worktrees

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 31, 2015, 22:00 UTC
Message-ID
<xmqqmvyc3s33.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1438379086.4735.25.camel@twopensource.com>
David Turner <dturner@twopensource.com> writes:
Show 5 quoted lines
> I further propose to add some patches (to go on top of the pseudorefs
> series):
>
> (a) include worktree-refs/ in per_worktree_refs and include
> worktree-refs/ in per_worktree_refs in common_list, and

Do you mean .git/worktree-refs/, just next to .git/refs? Then I think it makes sense.

> (b) include changes to bisect which switches it over to use
> worktree_refs/*.  To make this change compatible with bisections started
> with old git versions,...

I personally am not sure if it is worth the effort to cater to those who start bisection, stop and then upgrade their git version and expect to continue.

Previous: David Turner
Message 4 of 4 in “notes: handle multiple worktrees”
  1. notes: handle multiple worktreesDavid Turner, Jul 31, 2015
  2. Junio C HamanoJul 31, 2015
  3. David TurnerJul 31, 2015
  4. Junio C HamanoJul 31, 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.