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

Re: [bug] "git bisect old v3.0" takes 21 mins on Linux repo

From
ASAskar Safin <safinaskar@zohomail.com>
Date
Jan 17, 2025, 05:31 UTC
Message-ID
<19472bf2353.2c31e5fd10001.1997220058832133228@zohomail.com>
In-Reply-To
<xmqqo706u2z0.fsf@gitster.g>
I think "git bisect" is very important part of git.
Linux's "submitting-patches" contains this text:
> When dividing your change into a series of patches, take special care to ensure that the kernel builds and runs properly after each patch in the series. Developers using git bisect to track down a problem can end up splitting your patch series at any point; they will not thank you if you introduce bugs in the middle.
( https://docs.kernel.org/process/submitting-patches.html )
So, as you can see, existance of "git bisect" is rationale for contributor guidelines!
Contributor rules written the way they are because of "git bisect"!!!

-- Askar Safin https://types.pl/@safinaskar

Previous: Junio C HamanoNext: Jeff King
Message 8 of 10 in “[bug] "git bisect old v3.0" takes 21 mins on Linux repo”
  1. Askar SafinJan 13, 2025
  2. Askar SafinJan 13, 2025
  3. D. Ben KnobleJan 14, 2025
  4. Jeff KingJan 16, 2025
  5. Jeff KingJan 16, 2025
  6. Jeff KingJan 16, 2025
  7. Junio C HamanoJan 16, 2025
  8. Askar SafinJan 17, 2025
  9. Jeff KingJan 17, 2025
  10. Junio C HamanoJan 17, 2025

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.