this post was submitted on 07 Dec 2023
1400 points (91.7% liked)

linuxmemes

21197 readers
739 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    An oldie, but a goodie

    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 52 points 11 months ago* (last edited 11 months ago) (1 children)

    You can be polite or just straightforward and still get your message across.

    "We don't blame bugs on user programs", "This is not an error code that should be used here", "Your coding standards may have relaxed over your tenure, be sure to maintain quality code.", etc. I get the annoyance, but you can be firm without yelling, especially in a professional environment.

    Edit: Seeing the full context of Mauro's message (posted below), I can see why Linus took this tone. Mauro was being pretty condescending to a dev.

    [โ€“] [email protected] 12 points 11 months ago* (last edited 11 months ago)

    "We don't blame bugs on user programs"

    Linus says extra clear that the bug is not in user space, it's in kernel.