public inbox for
 help / color / mirror / Atom feed
From: Jerry D <>
To: Sam James <>,
Cc: GCC Mailing List <>,
Subject: Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 18:31:18 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 1/30/23 5:46 AM, Sam James wrote:
>> On 30 Jan 2023, at 06:27, Steve Kargl via Gcc <> 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

As long as your asking it just looks stupid, childish to think anyone 
needs an emoji in what we try think is a professional product. ( Too 
informal? )

If that's not enough, how about corny, or something for 12 year olds.

Yep, it's just stupid.  I don't have an issue with bots, I just don't 
need emojis outside of my personal chats on my phone.

If it is suppose to be a notification, how about just the word "Alert" 
or "Notice"




  reply	other threads:[~2023-01-31  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
     [not found] ` <>
     [not found]   ` <>
     [not found]     ` <>
2023-01-30 13:46       ` Sam James
2023-01-31  2:31         ` Jerry D [this message]
     [not found]       ` <>
     [not found]         ` <>
     [not found]           ` <>
     [not found]             ` <>
     [not found]               ` <>
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:

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

  git send-email \ \ \ \ \ \ \

* 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).