public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs fixes for 5.18-rc2
Date: Tue, 5 Apr 2022 19:38:53 +0200	[thread overview]
Message-ID: <20220405173853.GZ15609@suse.cz> (raw)
In-Reply-To: <CAADWXX-XPrfiD0TLGwMuzmGfs9pZ+HiTo1v9cs-mxb6x0OXpZw@mail.gmail.com>

On Tue, Apr 05, 2022 at 08:58:35AM -0700, Linus Torvalds wrote:
> On Tue, Apr 5, 2022 at 6:28 AM David Sterba <dsterba@suse.com> wrote:
> >
> > please pull the following fixes for btrfs, thanks.
> 
> Hmm. I got two copies of this...
> 
> ...and both were in my spam folder.
> 
> I don't see anything wrong with the message (spf and dkim both
> fine).so I assume it's something about suse.sz or suse.de that gmail
> doesn't like. Presumably some spammer sitting on a nearby network on
> the same ISP.

I don't know what could be wrong. Regular mails I send from mutt and the
pull request with 'git send-email'. Today I sent the first pull request
mail from mutt to see if there's a change from last time when you found
the mail in spam. The mail delivery took longer than expected, I think
more than half an hour which could be the gray listing period that I saw
on vger in the past. So I sent it again with git send-mail, just to be
sure. But if both end up in spam then it's probably something in the
mail body, other mails seem to be delivered.

> Anyway, not much you can do about it except perhaps ask whatever MIS
> people to see if they got put on some blacklist or whatever.
> 
> I've obviously noticed the pull request despite it being in my spam folder.

Good to know, thanks, I'll check if there's anything to do in my mail
setup.

  reply	other threads:[~2022-04-05 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 11:28 [GIT PULL] Btrfs fixes for 5.18-rc2 David Sterba
2022-04-05 13:24 ` David Sterba
2022-04-05 15:58 ` Linus Torvalds
2022-04-05 17:38   ` David Sterba [this message]
2022-04-06  6:08   ` Christoph Hellwig
2022-04-05 16:52 ` 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=20220405173853.GZ15609@suse.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=linux-btrfs@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