public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 23:44:27 +0100	[thread overview]
Message-ID: <8ecb95f7-c0d4-ac41-158a-6adc4d69d307@netcologne.de> (raw)
In-Reply-To: <976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com>

On 30.01.23 23:07, Gerald Pfeifer wrote:
> Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets
> to /dev/null?

Sending mail with special graphics in Subject lines is what spammers do,
to attract special attention.  (And no, umlauts are not included :-).

So, If I ever happen to break bootstrap, I will not learn about it from
a mail that uses spammer's techniques.  A regular mail, on the other
hand, I would read.

Regards

	Thomas


  reply	other threads:[~2023-01-30 22:44 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 [this message]
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=8ecb95f7-c0d4-ac41-158a-6adc4d69d307@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=gcc@gcc.gnu.org \
    /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).