All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Qemu Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: Separate notifications from list messages?
Date: Fri, 10 Jul 2020 09:54:54 +0100	[thread overview]
Message-ID: <20200710085454.GD4017912@redhat.com> (raw)
In-Reply-To: <008CCEB6-D3F4-4F1A-80DE-83F47873851F@livius.net>

On Fri, Jul 10, 2020 at 11:40:05AM +0300, Liviu Ionescu wrote:
> 
> 
> > On 10 Jul 2020, at 11:32, Peter Maydell <peter.maydell@linaro.org> wrote:
> > 
> > ... Do we expect any other
> > kinds to appear as we make more use of gitlab?
> 
> I have zero experience with gitlab, but on github yes, most project activity can trigger notifications.
> 
> this is not a problem in itself. the problem is that, instead of
> using a personal email address, the qemu-devel list was used
> somewhere in the project settings, and all notifications go to the list.

This wasn't a mistake - it was very delibrate, precisely so that all
involved in QEMU development will see the failures, instead of expecting
a handful of people to take all the work of dealing with failures. In
general anyone who's a regular contributor has a shared responsibility
to help keep QEMU building reliably.

Given the overall volume of mail on qemu-devel, a handful of notifications
from CI each day is not a burden IMHO.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-07-10  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09 18:14 Separate notifications from list messages? Liviu Ionescu
2020-07-10  4:19 ` Thomas Huth
2020-07-10  7:28   ` Liviu Ionescu
2020-07-10  8:09   ` Peter Maydell
2020-07-10  8:25     ` Liviu Ionescu
2020-07-10  8:32       ` Peter Maydell
2020-07-10  8:40         ` Liviu Ionescu
2020-07-10  8:54           ` Daniel P. Berrangé [this message]
2020-07-10  9:24             ` Liviu Ionescu
2020-07-10 11:43               ` Thomas Huth
2020-07-10 11:57                 ` Liviu Ionescu
2020-07-10  8:43         ` Philippe Mathieu-Daudé
2020-07-10  8:47           ` Liviu Ionescu
2020-07-10  8:49         ` Daniel P. Berrangé
2020-07-10  8:55           ` Liviu Ionescu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200710085454.GD4017912@redhat.com \
    --to=berrange@redhat.com \
    --cc=ilg@livius.net \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.