From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org, Frank Becker <fb@alien8.de>
Subject: Re: [GIT PULL] A minor amd64_edac fix for 3.13
Date: Sat, 16 Nov 2013 12:12:27 +0100 [thread overview]
Message-ID: <20131116111227.GD18306@pd.tnic> (raw)
In-Reply-To: <CA+55aFxHO9035t=CiNTRX1XK5KSxzh8HfZ3Kaspsm6yfs2O=8Q@mail.gmail.com>
On Sat, Nov 16, 2013 at 02:50:49AM -0800, Linus Torvalds wrote:
> As far as I can tell, only that one email had gotten caught by the
> spam filter. So it may be something in the body of the email itself,
> although I don't really see what that could be either..
Right.
> It happens occasionally, although it doors seem to happen much more to
> certain particular people than to others.
AFAIR, it had happened once before with a pull request a couple of
kernel releases back. Oh well, I will start sending the pull requests
from suse.de as their range is statically allocated and this should take
care of the dynamic IP range issues.
> The most common reason seems to be that your email provide is
> associated with spam, sometimes just because of a shared ISP.
Sure, it is one: https://www.hetzner.de/
> It is hard to tell with gmail, since it probably uses heuristics very
> much like spamassassin, but doesn't make the internal scores available
> (to avoid gaming them, I'm sure). So there are likely multiple small
> triggers that combine, rather than one single reason. With "possibly
> bad ISP" probably just being one of them..
Right, I'm adding Frank who takes care of it, just so he's aware.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-11-16 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 12:26 [GIT PULL] A minor amd64_edac fix for 3.13 Borislav Petkov
2013-11-16 2:02 ` Linus Torvalds
2013-11-16 10:06 ` Borislav Petkov
[not found] ` <CA+55aFxHO9035t=CiNTRX1XK5KSxzh8HfZ3Kaspsm6yfs2O=8Q@mail.gmail.com>
2013-11-16 11:12 ` Borislav Petkov [this message]
2013-11-16 18:10 ` Linus Torvalds
2013-11-16 18:23 ` Borislav Petkov
2013-11-16 23:34 ` Frank Becker
[not found] ` <CA+55aFxZcNfOEadD7EixNf5YZJVLTJ=2T4TOybWfwTP71KnuRg@mail.gmail.com>
2013-11-17 1:22 ` Frank Becker
2013-11-17 7:47 ` Borislav Petkov
2013-11-16 10:29 ` Borislav Petkov
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=20131116111227.GD18306@pd.tnic \
--to=bp@alien8.de \
--cc=fb@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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