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

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

From
BABen Aveling <bena.001@optusnet.com.au>
Date
Sep 19, 2013, 22:46 UTC
Message-ID
<523B7EB9.9050809@optusnet.com.au>
In-Reply-To
<523AF8EA.6080307@optusnet.com.au>
On 19/9/13 23:15, Ben Aveling wrote:
Show 9 quoted lines
> On 18/9/13 05:20, Junio C Hamano wrote:
>> Lukas Fleischer <git@cryptocrack.de> writes:
>>> why do we allow running git-checkout(1)
>>> from a subdirectory?
>> We may want to check the condition and forbid such a checkout.
> It would probably make sense.
> It might also make sense to relax the check in git bisect somewhat. 
> Currently, even "git bisect help" insists that "You need to run this 
> command from the toplevel of the working tree."

Probably also worth pointing out that whether or not the current shell is at toplevel, there can be other processes active in subdirectories.

     Regards, Ben
Previous: Ben AvelingNext: Junio C Hamano
Message 6 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.