From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/screen: security bump to version 4.9.1
Date: Wed, 23 Aug 2023 23:04:52 +0200 [thread overview]
Message-ID: <20230823230452.4552936c@windsurf> (raw)
In-Reply-To: <695d398827606c825566d544ee8665c5@free.fr>
Hello Julien,
On Wed, 23 Aug 2023 21:12:15 +0200
Julien Olivain <ju.o@free.fr> wrote:
> This is not a mistake. It is more an unfortunate technical issue. My
> original series was including a new screen runtime test in patch 2/2.
>
> I'll shortly explain, because this situation might happen again: my
> internet provider smtp (namely smtp.free.fr) decided few month ago to
> deploy an "AI based" anti-spam filter. Apparently, the thing was not
> trained enough on "git send-email" content. This generates many false
> positives, specifically on runtime tests. I'm working with the
> postmaster to solve the issue and complete this series when
> possible. Sorry about that.
Ah ah, so free.fr thinks you are spamming us with too many runtime
tests? :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-23 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 19:49 [Buildroot] [PATCH 1/2] package/screen: security bump to version 4.9.1 Julien Olivain
2023-08-22 21:41 ` Thomas Petazzoni via buildroot
2023-08-23 19:12 ` Julien Olivain
2023-08-23 21:04 ` Thomas Petazzoni via buildroot [this message]
2023-08-24 19:28 ` Julien Olivain
2023-08-24 20:38 ` Thomas Petazzoni via buildroot
2023-09-13 16:00 ` Peter Korsgaard
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=20230823230452.4552936c@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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