I've gone through the document and have been working through the ml for the past few years. When using the ml, putting CC in the message and invoking git send-email will cause it to also get sent to the stable ml so it wasn't clear to me that it would still work that way with a merge request. I saw my commit end up in the new stable releases though so I suppose that answers my question, i.e. cc in the message is sufficient for both ml and mr submissions.
Thanks - Chuck On Tue, May 7, 2019, 19:07 Marek Olšák <mar...@gmail.com> wrote: > There is a document about this in docs/, but I think you just need to add > the Cc: stable tag or the Fixes: tag to the commit message of all commits > you wanna nominate. > > Mare > > On Mon, May 6, 2019 at 12:12 PM Chuck Atkins <chuck.atk...@kitware.com> > wrote: > >> When doing an MR via GitLab, is adding the Cc: mesa-stable item enough to >> nominate it for inclusion in stable or does it still need to be separately >> sent to the stable mailing list? >> >> The question is specifically wrt >> https://gitlab.freedesktop.org/mesa/mesa/merge_requests/806 since I'd >> like to see the fix in the next stable release, but it's really a broader >> workflow question of how stable is dealt with while both the MR and ML >> processes are active. >> >> ---------- >> Chuck Atkins >> Staff R&D Engineer, Scientific Computing >> Kitware, Inc. >> >> _______________________________________________ >> mesa-dev mailing list >> mesa-dev@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/mesa-dev > >
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
