On Sun, 2018-06-03 at 12:02 -0500, mcatanz...@gnome.org wrote:
> On Sun, Jun 3, 2018 at 11:14 AM, Andre Klapper wrote:
> > Shall we allow them by default or will this be too much noise?
>
> The goal is to use release-team@ to assess whether it will be too much
> noise for desktop-devel@. I
Your pipeline has failed.
Project: gnome-build-meta ( https://gitlab.gnome.org/GNOME/gnome-build-meta )
Branch: master ( https://gitlab.gnome.org/GNOME/gnome-build-meta/commits/master
)
Commit: 201d1eca (
Your pipeline has failed.
Project: gnome-build-meta ( https://gitlab.gnome.org/GNOME/gnome-build-meta )
Branch: master ( https://gitlab.gnome.org/GNOME/gnome-build-meta/commits/master
)
Commit: 201d1eca (
Your pipeline has failed.
Project: gnome-build-meta ( https://gitlab.gnome.org/GNOME/gnome-build-meta )
Branch: master ( https://gitlab.gnome.org/GNOME/gnome-build-meta/commits/master
)
Commit: 201d1eca (
On Sun, Jun 3, 2018 at 11:14 AM, Andre Klapper wrote:
Shall we allow them by default or will this be too much noise?
The goal is to use release-team@ to assess whether it will be too much
noise for desktop-devel@. I would allow them for release-team@, for
sure, because the entire release
There are a bunch of posts in the moderation queue, such as:
> As list administrator, your authorization is requested for the
> following mailing list posting:
>
> List:release-team@
> From:gitlab-issues@
> Subject: gnome-build-meta | Pipeline #14101 has failed for master | 201d1eca
>
