Lines Matching full:about

190    soon or already was stamped "End-of-Life" (EOL) -- this usually happens about
230 with the change, but let all involved parties know about the risk. Hence, make
233 list about the risk, so everyone has the change on the radar in case reports
237 What else is there to known about regressions?
260 More about regression tracking and regzbot
291 duty: they need to tell regzbot about the regression report using the ``#regzbot
297 "Link:" tags to the patch description pointing to all reports about the issue
309 Do I have to tell regzbot about every regression I stumble upon?
315 while. Hence, it's best to tell regzbot about every regression, except when you
339 use regzbot to track severe issues, like reports about hangs, corrupted data,
383    or a ticket in a bug tracker that are slightly related, but about a different
401 Is there more to tell about regzbot and its commands?
404 More detailed and up-to-date information about the Linux
411 Quotes from Linus about regression
444        and simply not have to worry about it.
460        And notice that this is very much about *breaking* peoples environments.
498        about internal kernel API's, and the people who do that then also
508        The rules about regressions have never been about any kind of
511        The rules about regressions are always about "breaks user workflow".
536        The other side of the coin is that people who talk about "API
540        Again, the regression rule is not about documentation, not about
541        API's, and not about the phase of the moon.
543        It's entirely about "we caused problems for user space that used to work".
575        the kernel and never have to worry about it.
620        even care about.
627        upgrade random other tools that I don't even care about as I develop
693        What's instructive about it is that I reverted a commit that wasn't
723        consensus about the issue it exposed.
725        Take-away from the whole thing: it's not about whether you change the
726        kernel-userspace ABI, or fix a bug, or about whether the old code
727        "should never have worked in the first place". It's about whether