A question for experts on #git bisecting the #Linux #Kernel:
Assume someone runs into a regression when updating from 6.1.90[1] to 6.6.30 that needs bisecting. What do you suggest:
* Check manually which mainline release (e.g. 6.2, 6.3, ...) introduced the problem and afterwards bisect between that and the previous release.
* Bisect straight between 6.1 and 6.6.30.
1/ I guess I would definitely go for…
[1] let's assume that 6.1 was fine for this scenario to keep things simpler
Thorsten Leemhuis (acct. 1/4) /
npub1fz…emju7
2024-05-13 09:00:19
Author Public Key
npub1fzflkuaynm4r0fgzxpjky4t3266gm8es3cw34xtmlczwa3wt70us6emju7Published at
2024-05-13 09:00:19Event JSON
{
"id": "da4c95ea5749fcd209cfabd1010016ad46e43030b61e87ddecb2f38415374e22",
"pubkey": "4893fb73a49eea37a502306562557156b48d9f308e1d1a997bfe04eec5cbf3f9",
"created_at": 1715590819,
"kind": 1,
"tags": [
[
"t",
"git"
],
[
"t",
"linux"
],
[
"t",
"kernel"
],
[
"proxy",
"https://fosstodon.org/users/kernellogger/statuses/112432959935088852",
"activitypub"
]
],
"content": "A question for experts on #git bisecting the #Linux #Kernel:\n\nAssume someone runs into a regression when updating from 6.1.90[1] to 6.6.30 that needs bisecting. What do you suggest:\n\n* Check manually which mainline release (e.g. 6.2, 6.3, ...) introduced the problem and afterwards bisect between that and the previous release.\n\n* Bisect straight between 6.1 and 6.6.30.\n\n1/ I guess I would definitely go for…\n\n[1] let's assume that 6.1 was fine for this scenario to keep things simpler",
"sig": "4d02d7df15f3adbe2fb152948d46d4ab498c1795fe6482bdf3857de001d5a3203ec98579e65149168fbe2f97faf71381799a54a0f715339a359a268a83dd8cd2"
}