According to "Patch Rejection in Firefox", before Mozilla introduced integration repositories in

$2$

$0$

$1$

$1$

$,$

$$why would a developer need to backout a problematic commit as soon as possible?

$($

Select all correct answers.

$)$

If the commit was left on the server too long, it became permanent and cannot be removed without an eviction notice.

Other developers relied on the code in the central repo to write their own patches. If that code fails in build or tests, other patches cannot be tested properly.

The problematic commit might be leaked online and users would lose confidence in the product.

The developer should remove it as fast as possible before the other developers see it and make fun of them.