From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: LIU Hao <lh_mouse@126.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
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 12:18:12 -0800 [thread overview]
Message-ID: <Y9l3hFXdJnENEHJM@troutmask.apl.washington.edu> (raw)
In-Reply-To: <f5c0804d-508f-cee1-c5a7-fc1f8a36ac54@126.com>
On Tue, Jan 31, 2023 at 10:38:02PM +0800, LIU Hao wrote:
> 在 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.
>
The irony! Your email ended up in one of my spam folders.
X-junkfilter: 20020519
X-Spammer: bodychk-domains: 126.com>
domains: 126.com
--
Steve
prev parent reply other threads:[~2023-01-31 20:18 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
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 [this message]
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=Y9l3hFXdJnENEHJM@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=buildbot@sourceware.org \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=jvdelisle2@gmail.com \
--cc=lh_mouse@126.com \
--cc=mark@klomp.org \
--cc=sam@gentoo.org \
--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).