From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] trace: only permit standard C types and fixed size integer types
Date: Wed, 7 Mar 2018 10:18:37 +0000 [thread overview]
Message-ID: <20180307101837.GG20201@redhat.com> (raw)
In-Reply-To: <20180307012430.GC13844@lemon.usersys.redhat.com>
On Wed, Mar 07, 2018 at 09:24:30AM +0800, Fam Zheng wrote:
> On Tue, 03/06 16:22, Daniel P. Berrangé wrote:
> > RFE for patchew...
> >
> > Now we're sending separate email alerts for each build job, can we
> > make patchew include the job name in the subject line, so it is
> > immediately obvious which job failed without needing to read the
> > body.
>
> Yes, doable. Do we still want the original subject (The "Re: ..." part)? If so,
> any idea what is a good format for the full subject line?
Perhaps take the original Subject, and prefix it. eg something like
this:
Subject: s390-build failed (Re: [Qemu-devel] [PATCH] trace: only permit standard C types and...)
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 :|
next prev parent reply other threads:[~2018-03-07 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 15:46 [Qemu-devel] [PATCH] trace: only permit standard C types and fixed size integer types Daniel P. Berrangé
2018-03-06 16:05 ` no-reply
2018-03-06 16:20 ` Daniel P. Berrangé
2018-03-07 1:27 ` Fam Zheng
2018-03-06 16:12 ` no-reply
2018-03-06 16:22 ` Daniel P. Berrangé
2018-03-07 1:24 ` Fam Zheng
2018-03-07 10:18 ` Daniel P. Berrangé [this message]
2018-03-06 16:16 ` no-reply
2018-03-06 16:20 ` no-reply
2018-03-06 17:20 ` no-reply
2018-03-06 18:44 ` Philippe Mathieu-Daudé
2018-03-07 12:45 ` Stefan Hajnoczi
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=20180307101837.GG20201@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.