All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linux Security Module list 
	<linux-security-module@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Austin Kim <austindh.kim@gmail.com>,
	Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Subject: Re: [GIT PULL] Smack patches for v5.15
Date: Tue, 31 Aug 2021 12:15:37 -0700	[thread overview]
Message-ID: <CAADWXX9A-6R13VAekvzvWYGcy990nLxcyz1BiZyeBpKHivtCqg@mail.gmail.com> (raw)
In-Reply-To: <ff60d9aa-28b9-9c6d-f318-94dd51a95abd@schaufler-ca.com>

On Tue, Aug 31, 2021 at 11:53 AM Casey Schaufler <casey@schaufler-ca.com> wrote:
>
> Here is the Smack pull request for v5.15.

Hmm. This went into my spambox.

I have no idea why. Everything looks ok as far as I can tell, although
having a SPF record for the originating host might have helped.

It also doesn't look like you are doing anything new wrt your email
setup, even if that yahoo web mail thing might be a bit unusual.

It *might* help to use "git://" instead of "https://" in case some
spam logic thinks web links might be more suspicious, but who knows..

Anyway, I've caught it and marked it not spam, but this is a note to
let you know that something on the internet hates you and your emails.

              Linus

  reply	other threads:[~2021-08-31 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ff60d9aa-28b9-9c6d-f318-94dd51a95abd.ref@schaufler-ca.com>
2021-08-31 18:53 ` [GIT PULL] Smack patches for v5.15 Casey Schaufler
2021-08-31 19:15   ` Linus Torvalds [this message]
2021-08-31 20:06   ` pr-tracker-bot

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=CAADWXX9A-6R13VAekvzvWYGcy990nLxcyz1BiZyeBpKHivtCqg@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=austindh.kim@gmail.com \
    --cc=casey@schaufler-ca.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tianjia.zhang@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.