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

Re: https://github.com/rust-lang/rust is not bisectable

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Dec 17, 2022, 16:34 UTC
Message-ID
<878rj6rnuo.fsf@igel.home>
In-Reply-To
<CAPnZJGABhczzs-6Pri2SAOkujJXT1+JDH9FiwdDns6=miZmvFQ@mail.gmail.com>
On Dez 17 2022, Askar Safin wrote:
> Okay, so "git bisect" gave us commit
> 26562973b3482a635416b2b663a13016d4d90e20. And here I see a bug:
> 7175c499ecc32cb3ff713be0bbac9fd12990a34e is NOT ancestor of
> 26562973b3482a635416b2b663a13016d4d90e20!

26562973b3482a635416b2b663a13016d4d90e20 is an ancestor of the bad commit, and not an ancestor of the good commit, thus it is a candidate for introducing the bad condition. In a non-linear history, there can be multiple good commits that are not directly related, each one cutting out branches from the history.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."
Previous: Askar SafinNext: Askar Safin
Message 2 of 9 in “https://github.com/rust-lang/rust is not bisectable”
  1. Askar SafinDec 17, 2022
  2. Andreas SchwabDec 17, 2022
  3. Askar SafinDec 18, 2022
  4. Andreas SchwabDec 18, 2022
  5. SZEDER GáborDec 18, 2022
  6. Askar SafinDec 18, 2022
  7. Andreas SchwabDec 18, 2022
  8. SZEDER GáborDec 18, 2022
  9. rsbecker@nexbridge.comDec 18, 2022

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.