Closed derekbruening closed 5 months ago
Technically speaking, we don't know if it breaks the build, thus the description is inaccurate. The patch is just being conservative.
Technically speaking, we don't know if it breaks the build, thus the description is inaccurate. The patch is just being conservative.
We do know as it requires an extra step to remove the patch file and the patch fails to apply (by inspection, plus the patch failed when I tested my PR #6626 so we know it fails).
Reasonable to have TBR here IMHO to get the repo back to a pull-able state quickly.
This reverts commit 984e33548cde2b9869d16a60b15383c494470386 as it breaks our internal build.
Issue: #6627