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 17, 2013, 17:27 UTC
Message-ID
<xmqqbo3rz7ca.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAJTo0LZ=bNNUc8O=bDDOp2vudsc_wL+-nqsXW5r1rq3H7M0e7Q@mail.gmail.com>
"Burton, Ross" <ross.burton@intel.com> writes:
Show 5 quoted lines
> Why does git-bisect need to be ran from the top level of the working
> tree?  It sources git-sh-setup.sh which sets GIT_DIR, which
> git-bisect.sh then appears to consistently use.  Is there a reason for
> needing to be at the top-level, or is this an old and redundant
> message?
A wild guess.

Imagine if you start from a subdirectory foo/ but the directory did not exist in the older part of the history of the project. When bisect needs to check out a revision that was older than the first revision that introduced that subdirectory, what should happen? Worse yet, if "foo" was a file in the older part of the history, what should happen?

Previous: Burton, RossNext: Lukas Fleischer
Message 2 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.