3 ms·

I just did a quick check the posted fix is not in the most recent -rc branch in the public git repo.

• londons_explore 5y ago
  This is the issue with using mailing lists... Large numbers of perfectly good fixes, embodying many hours of effort, just get missed and forgotten about. At least with GitHub PR's, every request either needs to be merged or rejected.
  • loeg 5y ago
    I’m no fan of mailing lists, but GitHub PRs get ignored in much the same way.
    • misnome 5y ago
      There’s ignored, and there is “not aware that it’s unresolved”. How do mailing list flows handle the “give me a list of open patches”?
      • colonwqbang 5y ago
        People treat emails like tickets, representing things that should be done. They put them in particular email directories depending on their personal workflow. When they are either done or rejected, they delete the email, archive it, or mark it as read. It's not unlike the github workflow except that it's up to each person to define the way they prefer to work. Not a single policy that's decided by the project owner. Planning/tracking also happens more in private instead of public. You may think that's worse, but perhaps you can also see why some might prefer it?
  • Denvercoder9 5y ago
    The modern trend is autoclosing PR's after they haven't had any activity in X months, so there's not much difference with mailing lists anymore...