[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181229153608.GA21173@pure.paranoia.local>
Date: Sat, 29 Dec 2018 10:36:08 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: "Williams, Dan J" <dan.j.williams@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
Subject: Re: [GIT PULL] libnvdimm for 4.21
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@...ux-foundation.org" <torvalds@...ux-foundation.org>
> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
> "linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.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
Powered by blists - more mailing lists