Lines Matching full:something
296 sure to do something that was expected long before regzbot came to light: add
312 Ideally yes: we are all humans and easily forget problems when something more
314 kernel or something in real life that's keeping us away from keyboards for a
472 But if something actually breaks, then the change must get fixed or
501 up". Whoever broke something gets to fix it too.
524 And obviously, if users take years to even notice that something
531 code was in staging or because the man-page said something else) is
581 Guys, whether something was buggy or not DOES NOT MATTER.
586 something because we were fixing a bug" is completely insane. We fix
588 we can break something is simply NOT TRUE.
609 It's basically saying "I took something that worked, and I broke it,
619 MUCH BIGGER bug by "fixing" something that the user clearly didn't
728 something breaks existing users' workflow.