Linux 5.12's very bad, double ungood day
Linux 5.12's very bad, double ungood day
Posted Mar 8, 2021 20:28 UTC (Mon) by pebolle (guest, #35204)In reply to: Linux 5.12's very bad, double ungood day by luto
Parent article: Linux 5.12's very bad, double ungood day
- restart at v5.11;
- add everything in v5.12-rc1-dontuse except the misguided commit;
- add the misguided commit and it's fix squashed as a single commit;
- add everything else that is now in v5.12-rc2 but not in v5.12-rc1-dontuse.
That should make v5.12-rc1-dontuse a dead end which no-one would ever hit while bisecting. (And v5.12-rc2 basically a second try at a v5.12-rc1.) Or doesn't git work like that?
Posted Mar 8, 2021 21:13 UTC (Mon)
by josh (subscriber, #17465)
[Link]
Posted Mar 8, 2021 21:16 UTC (Mon)
by geert (subscriber, #98403)
[Link] (3 responses)
Posted Mar 9, 2021 8:46 UTC (Tue)
by marcH (subscriber, #57642)
[Link]
That's the goal.
Posted Mar 9, 2021 10:21 UTC (Tue)
by pr1268 (guest, #24648)
[Link] (1 responses)
But, in this particular case, he's making an exception. From our editor's article (emphasis mine):
Posted Mar 9, 2021 10:44 UTC (Tue)
by geert (subscriber, #98403)
[Link]
Linux 5.12's very bad, double ungood day
Linux 5.12's very bad, double ungood day
Linux 5.12's very bad, double ungood day
Linux 5.12's very bad, double ungood day
Following your approach would rebase the master branch [...], which is something Linus does not want to do ever.
That sort of rebasing would normally be frowned upon, but Torvalds made it clear that it is permissible — and expected — this time.
Linux 5.12's very bad, double ungood day
If Linus had been comfortable about rebasing his own master branch, he would have done so for sure.