<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   pinchartl: <u>syoung</u>: that doesn't mean rebasing complete subsystem trees though, only topic branches that are based on top of -rc1
   <br> (as far as I understand)
   <br> but we only have one topic branch effectively
   <br> onto which we've merged -rc2
   <br> so rebasing that wouldn't be too bad
   syoung: come to think it, it might be useful if you could have a .gitbisect file which can list commits to avoid, i.e. "this will eat your disk" kind of commits
   <br> so git bisect has enough information to avoid this problem rather than coaxing git history in the right direction
   <br> Ingo's follow-up is pretty unambiguous https://lwn.net/ml/linux-kernel/20210306125437.GA436274@gmail.com/