From: Thomas Koenig <tkoenig@netcologne.de>
To: Mark Wielaard <mark@klomp.org>,
sgk@troutmask.apl.washington.edu,
Sam James via Fortran <fortran@gcc.gnu.org>
Cc: Jerry D <jvdelisle2@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 15:46:30 +0100 [thread overview]
Message-ID: <1cac0dec-e9c1-e721-52bd-40eb6b8676de@netcologne.de> (raw)
In-Reply-To: <e5e8e6d1dbde5e24246eba9b964b3af3627a6ee3.camel@klomp.org>
On 30.01.23 14:52, Mark Wielaard wrote:
> Hi Steve,
>
> On Sun, 2023-01-29 at 22:27 -0800, Steve Kargl via Gcc wrote:
>> Please remove the skull and cross bones in the subject line.
>
> That is the default "hazard symbol" buildbot uses if a build turns from
> success to failure. If you have a better suggestion you might want to
> contact upstream https://buildbot.net/ We'll pick up the new default
> when we'll upgrade.
>
> Or if you think we should use a custom email template:
> https://docs.buildbot.net/latest/manual/configuration/report_generators/formatter.html
> You can provide a patch to buildbot@sourceware.org.
> The code for our instance can be found here:
> https://sourceware.org/git/builder.git
I usually put e-mails with such unicode characters into my spam folder
automatically.
If that's what you want, that is fine with me.
Regards
Thomas
next prev parent reply other threads:[~2023-01-30 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230129193123.51BDE3858D35@sourceware.org>
2023-01-29 19:36 ` Fwd: ☠ " Jerry D
2023-01-29 19:43 ` NightStrike
2023-01-29 19:49 ` Sam James
2023-01-30 6:27 ` Steve Kargl
2023-01-30 13:46 ` Sam James
2023-01-31 2:31 ` Jerry D
2023-01-30 13:52 ` Mark Wielaard
2023-01-30 14:46 ` Thomas Koenig [this message]
2023-01-30 15:10 ` Steve Kargl
2023-01-30 22:07 ` Gerald Pfeifer
2023-01-30 22:44 ` Thomas Koenig
2023-01-30 22:50 ` Steve Kargl
2023-01-31 13:13 ` Thomas Schwinge
2023-01-31 14:38 ` LIU Hao
2023-01-31 20:18 ` Steve Kargl
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=1cac0dec-e9c1-e721-52bd-40eb6b8676de@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
--cc=mark@klomp.org \
--cc=sgk@troutmask.apl.washington.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).