emrekultursay added a comment. Sure, you are right that it should be pulled back into release/16.x, and I expect it to apply cleanly. However, I don't know what mechanism should bve used to create cherry-pick changes into release branches on GitHub: (1) this was not a GitHub issue/PR, so I guess I cannot use that mechanism; (2) I can run `git cherry-pick` myself, and then run `arc diff` to create a new Phabricator review (with a new D number?) but I don't know if that's the right way, (3) maybe there's some special "arc" commands to create a cherry-pick? (4) any other way?
Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D144240/new/ https://reviews.llvm.org/D144240 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
