From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [put pull] timestamp stuff
Date: Wed, 5 Feb 2020 11:08:01 -0500 [thread overview]
Message-ID: <20200205160801.x3hr3ziwz2ffxltt@chatter.i7.local> (raw)
In-Reply-To: <CAHk-=wivZdF6tNERQp+CXyz7zeN4uG9O4d7mZhCrp3anJ29Arg@mail.gmail.com>
On Wed, Feb 05, 2020 at 06:53:07AM +0000, Linus Torvalds wrote:
> But pr-tracker-bot _also_ isn't responding to the one where that
> wasn't the case:
>
> [git pull] kernel-initiated rm -rf on ramfs-style filesystems
>
> and I'm not seeing why that one wasn't picked up. But it seems to be
> because it never made it to lore.
>
> I see
>
> To: Linus Torvalds <torvalds@linux-foundation.org>
> Cc: fsdevel.@zeniv.linux.org.uk, linux-kernel@vger.kernel.org
> Subject: [git pull] kernel-initiated rm -rf on ramfs-style filesystems
> Message-ID: <20200204150912.GS23230@ZenIV.linux.org.uk>
>
> on that other message in my mailbox, but I don't see it on lore. Odd.
> Is it because the "fsdevel" address is mis-spelled on the Cc line?
> Strange.
That message-id doesn't appear to have traversed the mail system, so my
guess would be that it didn't make it past some upstream MTA -- either
vger or the one before it. The fact that this messages is not on
lkml.org either seems to confirm that theory.
Best,
-K
next prev parent reply other threads:[~2020-02-05 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:00 [put pull] timestamp stuff Al Viro
2020-02-05 6:53 ` Linus Torvalds
2020-02-05 16:08 ` Konstantin Ryabitsev [this message]
2020-02-05 16:25 ` Al Viro
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=20200205160801.x3hr3ziwz2ffxltt@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).