Thread

1. bitpush · 1790973564 · focus · HN ↗

   Why wont GOS contribute this to upstream?

   1. BlackRabbit1 · 1790973756 · focus · HN ↗

      Because Google is already picking patches from GOS ;-)

      1. bitpush · 1790974081 · focus · HN ↗

         I'm confused, so if open source is working as expected then what's the point of the blogpost?

         1. Dylan16807 · 1790974753 · focus · HN ↗

            It's a post about google screwing up their process and also pushing a bad update to a ton of people, and other people cleaning up their mess. I'm glad "open source is working" but that's a small part of the picture and I don't see why that would remove the point of the blog post.

            1. bitpush · 1790979142 · focus · HN ↗

               [dead]

               1. Dylan16807 · 1790980477 · focus · HN ↗

                  Major performance bugs don't sneak themselves into releases and then prevent followup fixes from being promptly released.

                  The point of the post is not that grapheneos made the fix, it's that they had to.

      2. HybridStatAnim8 · 1791051478 · focus · HN ↗

         Citation needed.

         1. Andromxda · 1791096196 · focus · HN ↗

            I think they're referring to past contributions to AOSP from GrapheneOS developers.

Unofficial Hacker News client; not affiliated with Y Combinator.