From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [GIT PULL] libnvdimm for 4.21
Date: Sat, 29 Dec 2018 10:36:08 -0500 [thread overview]
Message-ID: <20181229153608.GA21173@pure.paranoia.local> (raw)
In-Reply-To: <CAHk-=wgMfBXdiaeAxYrdTq9VoaVgN26T8MU7+3EnvJP_e0byuw@mail.gmail.com>
On Fri, Dec 28, 2018 at 09:57:28PM -0800, Linus Torvalds wrote:
> Hmm.
>
> This pull request doesn't seem to have gotten an automatic pr-tracker
> reply, even though I pulled it, and even though it was cc'd to lkml.
>
> Konstantin, any idea why the automation didn't trigger? I'm not seeing
> anything all that odd about it.
As you've noticed, it's not on lore, and it's also not on any other LKML
archive out there (I've checked lkml.org, lkml.iu.edu, marc.info). So,
I'm not sure precisely what happened, but it would appear that despite
the CC in the headers, the mail never actually passed vger.
> Does lkml hate Dan?
>
> Headers say
>
> To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
> CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
> "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
I wonder if vger doesn't properly process "CC" headers when both letters
are caps, but it's a very thin guess. As I don't have any access to
vger, I can't shed much more light on this either.
-K
next prev parent reply other threads:[~2018-12-29 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4880b31d0d32c38a675048be903814a062907125.camel@intel.com>
2018-12-29 5:57 ` Linus Torvalds
2018-12-29 15:36 ` Konstantin Ryabitsev [this message]
2018-12-29 18:04 ` Dan Williams
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=20181229153608.GA21173@pure.paranoia.local \
--to=konstantin@linuxfoundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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
all inboxes | Powered by JetHome®