From: Gerald Pfeifer <gerald@pfeifer.com>
To: Steve Kargl <sgk@troutmask.apl.washington.edu>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
Mark Wielaard <mark@klomp.org>,
Sam James via Fortran <fortran@gcc.gnu.org>,
Jerry D <jvdelisle2@gmail.com>,
gcc@gcc.gnu.org
Subject: Re: Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 30 Jan 2023 23:07:46 +0100 (CET) [thread overview]
Message-ID: <976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com> (raw)
In-Reply-To: <Y9fd2SBZuEKOc0TF@troutmask.apl.washington.edu>
On Mon, 30 Jan 2023, Steve Kargl via Gcc wrote:
> Bingo. In the case of non-[a-zA-Z] characters in the
> Subject (or Fromi or To) line, the spam folder is normally
> named /dev/null.
Hmm, so any digit, parenthesis, or bracket in the Subject, and mails gets
to /dev/null?
Or having an umlaut or other special character in one's name - which is
pretty common in parts of the world like Central Europe?
"Be conservative in what you send, be liberal in what you accept."
[Postel's Law]
Gerald
next prev parent reply other threads:[~2023-01-30 22:07 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 [this message]
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=976efc37-8d08-a1bd-40d4-e6d9af299697@pfeifer.com \
--to=gerald@pfeifer.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jvdelisle2@gmail.com \
--cc=mark@klomp.org \
--cc=sgk@troutmask.apl.washington.edu \
--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).