From: LIU Hao <lh_mouse@126.com>
To: Thomas Schwinge <thomas@codesourcery.com>,
sgk@troutmask.apl.washington.edu
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
Thomas Koenig <tkoenig@netcologne.de>,
Mark Wielaard <mark@klomp.org>, Sam James <sam@gentoo.org>,
fortran@gcc.gnu.org, Jerry D <jvdelisle2@gmail.com>,
gcc@gcc.gnu.org, buildbot@sourceware.org
Subject: Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Tue, 31 Jan 2023 22:38:02 +0800 [thread overview]
Message-ID: <f5c0804d-508f-cee1-c5a7-fc1f8a36ac54@126.com> (raw)
In-Reply-To: <87zg9yx2xq.fsf@euler.schwinge.homeip.net>
[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]
在 2023-01-31 21:13, Thomas Schwinge 写道:
> Hi!
>
> On 2023-01-30T14:50:08-0800, Steve Kargl via Fortran <fortran@gcc.gnu.org> wrote:
>> Does the skull and crossbones convey anymore info than the rest of
>> the subject line
>>
>> Buildbot (Sourceware): gcc - failed configure (failure) (master)
>
> They convey as much additional information as does (automated) colorful
> syntax highlighting, or (manual) source code line indentation: "none" to
> some, "a lot" to others.
>
>
First, I'd argue that 'emoji characters imply spammer' makes little sense. Everyone can examine the
source of all messages in this thread and their `X-Spam-Status` headers. The fact is that, so far no
message had been given a tag for having emoji/bad/obfuscated characters in its subject.
Second, I also agree that the skull carries NO additional information. What happened? Where did it
happen? How severe was it? What should we do about it? A skull is neither descriptive nor
informative, and is very unfriendly for message filters. A tag there might look much more helpful,
such as [BUILDBOT] or [FAIL].
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2023-01-31 15:13 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
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 [this message]
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=f5c0804d-508f-cee1-c5a7-fc1f8a36ac54@126.com \
--to=lh_mouse@126.com \
--cc=buildbot@sourceware.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jvdelisle2@gmail.com \
--cc=mark@klomp.org \
--cc=sam@gentoo.org \
--cc=sgk@troutmask.apl.washington.edu \
--cc=thomas@codesourcery.com \
--cc=tkoenig@netcologne.de \
/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).