Re: [bug] "git bisect old v3.0" takes 21 mins on Linux repo
- From
- Askar 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