• aksdb@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    6 天前

    It was an example. I don’t have a fucking clue how all the maintainers are named.

    The main question was: why can a maintainer NACK something not in their responsibility? Isn’t it simply necessary to find one maintainer who is fine with it and pulls it in?

    Or even asked differently: shouldn’t you need to find someone who ACKs it rather than caring about who NACKs it?

    • LeFantome@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 天前

      Let me just say that hierarchies are for breaking ties.

      The normal process is that Linus prefers we all work through maintainers to cut down on the noise that comes to him. In this case, the maintainer is the reason the noise is coming to Linus. So, it will be up to him to settle it.