From: Jerry D <jvdelisle2@gmail.com>
To: Sam James <sam@gentoo.org>, sgk@troutmask.apl.washington.edu
Cc: GCC Mailing List <gcc@gcc.gnu.org>, buildbot@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 18:31:18 -0800 [thread overview]
Message-ID: <37cfbd5c-f512-b05c-754a-ad1da6119ad3@gmail.com> (raw)
In-Reply-To: <673D785C-6956-4857-B497-FF4D6351EF17@gentoo.org>
On 1/30/23 5:46 AM, Sam James wrote:
>
>
>> 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
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"
Regards,
Jerry
Jerry
next prev parent reply other threads:[~2023-01-31 2:31 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 [this message]
2023-01-30 13:52 ` Mark Wielaard
2023-01-30 14:46 ` Thomas Koenig
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=37cfbd5c-f512-b05c-754a-ad1da6119ad3@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=buildbot@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=sam@gentoo.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).