Yes, PR's do have to be rebased on the master / main branch while waiting to be merged occasionally. That's how it works.
Sent with [Proton Mail](https://proton.me/) secure email. ------- Original Message ------- On Sunday, July 30th, 2023 at 12:31 PM, tioguda <guda.fla...@gmail.com> wrote: > This merge request makes no sense, as the translation patch has to be updated > as upstream sends new commits. > > Upstream doesn't support translations, so I hope the packages don't get > merged. > > On Jul 30 2023, at 12:52 pm, Mark Wagie <mark.wa...@proton.me> wrote: > >> Actually, it would be better to submit an upstream Pull Request instead. >> >> Sent with Proton Mail secure email. >> >> ------- Original Message ------- >> On Sunday, July 30th, 2023 at 9:48 AM, not...@aur.archlinux.org >> <not...@aur.archlinux.org> wrote: >> >>> yochananmarqos [1] filed a request to merge spectre-meltdown-checker- >>> pt-br [2] into spectre-meltdown-checker [3]: >>> >>> Please ask the spectre-meltdown-checker maintainer to add the patch >>> instead of creating a duplicate package. >>> >>> [1] https://aur.archlinux.org/account/yochananmarqos/ >>> [2] https://aur.archlinux.org/pkgbase/spectre-meltdown-checker-pt-br/ >>> [3] https://aur.archlinux.org/pkgbase/spectre-meltdown-checker/ > > [Sent from Mailspring]
