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

Re: [PATCH/RFC 0/2] bisect per-worktree

From
David Turner <dturner@twopensource.com>
Date
Aug 1, 2015, 05:43 UTC
Message-ID
<1438407797.4735.30.camel@twopensource.com>
In-Reply-To
<CAP8UFD0aCSW3JxneHvSEE3T6zQtgipp5nhWT9VpMqHAmzd_e3Q@mail.gmail.com>
On Sat, 2015-08-01 at 06:04 +0200, Christian Couder wrote:
Show 14 quoted lines
> 
> Le 1 août 2015 09:01, "David Turner" <dturner@twopensource.com> a
> écrit :
> >
> > This is RFC because I'm not sure why show-ref only works on refs/
> (and
> > whether it should learn to look in worktree-refs/).  I'm also not
> sure
> > whether there are other changes I should make to refs.c to handle
> > per-worktree refs; I basically did the simplest thing I could think
> of
> > to start with.
> 
> (Sorry, I am answering from my phone, as I am having a vacation. )
Enjoy your vacation.
> I wonder what would happen if people upgrade in the middle of a
> bisection or if they have scripts using "bisect/bad" for example.
Junio told me not to worry about this, so I didn't.
Message 1 of 1 in “Re: [PATCH/RFC 0/2] bisect per-worktree”
  1. David TurnerAug 1, 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.