public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: sgk@troutmask.apl.washington.edu
Cc: Jerry D <jvdelisle2@gmail.com>,
	GCC Mailing List <gcc@gcc.gnu.org>,
	buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 13:46:29 +0000	[thread overview]
Message-ID: <673D785C-6956-4857-B497-FF4D6351EF17@gentoo.org> (raw)
In-Reply-To: <Y9djb4iMA8kySL0F@troutmask.apl.washington.edu>

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]



> On 30 Jan 2023, at 06:27, Steve Kargl via Gcc <gcc@gcc.gnu.org> wrote:

Hi Steve,

> Please remove the skull and cross bones in the subject line.

This is a sourceware project so I've CC'd the buildbot mailing list where we discuss
these matters.

Does the emoji bother you, or is it the skull and crossbones specifically (which is
a recognised symbol for a hazard)?

Note that this is the default upstream from the Buildbot project (we use their
software) too. We haven't chosen it ourselves.

Thanks,
sam

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

       reply	other threads:[~2023-01-30 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230129193123.51BDE3858D35@sourceware.org>
     [not found] ` <1985b16e-f17d-bba6-8b57-d372f1741356@gmail.com>
     [not found]   ` <1EC379D7-6EF4-4B27-9D8C-00CFFD115F44@gentoo.org>
     [not found]     ` <Y9djb4iMA8kySL0F@troutmask.apl.washington.edu>
2023-01-30 13:46       ` Sam James [this message]
2023-01-31  2:31         ` Jerry D
     [not found]       ` <e5e8e6d1dbde5e24246eba9b964b3af3627a6ee3.camel@klomp.org>
     [not found]         ` <1cac0dec-e9c1-e721-52bd-40eb6b8676de@netcologne.de>
     [not found]           ` <Y9fd2SBZuEKOc0TF@troutmask.apl.washington.edu>
     [not found]             ` <976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com>
     [not found]               ` <Y9hJoAKNPFU65saq@troutmask.apl.washington.edu>
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=673D785C-6956-4857-B497-FF4D6351EF17@gentoo.org \
    --to=sam@gentoo.org \
    --cc=buildbot@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --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).