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

Re: Bisect needing to be at repo top-level?

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 19, 2013, 23:04 UTC
Message-ID
<xmqqpps4qups.fsf@gitster.dls.corp.google.com>
In-Reply-To
<523B7EB9.9050809@optusnet.com.au>
Ben Aveling <bena.001@optusnet.com.au> writes:
> Probably also worth pointing out that whether or not the current shell
> is at toplevel, there can be other processes active in subdirectories.
That is not something we have control over anyway.
Previous: Ben AvelingNext: Stefan Beller
Message 7 of 11 in “Bisect needing to be at repo top-level?”
  1. Burton, RossSep 17, 2013
  2. Junio C HamanoSep 17, 2013
  3. Lukas FleischerSep 17, 2013
  4. Junio C HamanoSep 17, 2013
  5. Ben AvelingSep 19, 2013
  6. Ben AvelingSep 19, 2013
  7. Junio C HamanoSep 19, 2013
  8. Stefan BellerOct 9, 2013
  9. Jeff KingOct 9, 2013
  10. Stefan BellerOct 9, 2013
  11. Burton, RossSep 17, 2013

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.