unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Eric Wong <e@80x24.org>
Cc: <meta@public-inbox.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: https://lore.kernel.org/linux-mm/
Date: Wed, 7 Jun 2023 10:41:18 +0800	[thread overview]
Message-ID: <844f09ab-8a21-063b-3a81-aa655ab4a523@intel.com> (raw)
In-Reply-To: <20230607023016.M573921@dcvr>



On 6/7/2023 10:30 AM, Eric Wong wrote:
> "Yin, Fengwei" <fengwei.yin@intel.com> wrote:
>> On 6/7/2023 8:07 AM, Eric Wong wrote:
>>> I suspect problems at kernel.org on May 31 caused kvack.org to
>>> unsubscribe the account lore was using to receive messages.
>>> Help from other subscribers will be necessary to restore
>>> messages dropped during the gap.
>>
>> Do you mean subscribed to linux-mm? My colleagues and I did subscribe
>> linux-mm. Just let me know how we can help here. Thanks.
> 
> Messages on lore.kernel.org show up because an email address
> they control receives messages from the linux-mm list.  Since
> (I assume) kvack.org is controlled by someone else, kernel.org
> needs to subscribe to the linux-mm list just like you or anyone
> else.
Oh. So the problem is kernel.org does not subscribe to linux-mm
after May 31st? Thanks.


Regards
Yin, Fengwei

> 
> kernel.org either runs public-inbox-mda or public-inbox-watch to
> inject messages they receive from linux-mm into the public-inbox.
> So, something like this:
> 
>    https://public-inbox.org/flow.txt
> 
> (the entire lore.kernel.org setup is 100% reproducible using
> public-inbox software)

  reply	other threads:[~2023-06-07  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  8:05 https://lore.kernel.org/linux-mm/ Yin Fengwei
2023-06-07  0:07 ` https://lore.kernel.org/linux-mm/ Eric Wong
2023-06-07  1:39   ` https://lore.kernel.org/linux-mm/ Yin, Fengwei
2023-06-07  2:30     ` https://lore.kernel.org/linux-mm/ Eric Wong
2023-06-07  2:41       ` Yin, Fengwei [this message]
2023-06-07 13:45         ` https://lore.kernel.org/linux-mm/ Konstantin Ryabitsev
2023-06-08  1:30           ` https://lore.kernel.org/linux-mm/ Yin Fengwei
2023-06-08  6:40           ` https://lore.kernel.org/linux-mm/ Jonathan Corbet
2023-06-08 19:24             ` https://lore.kernel.org/linux-mm/ Konstantin Ryabitsev
2023-06-07  2:53       ` https://lore.kernel.org/linux-mm/ Yin, Fengwei

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=844f09ab-8a21-063b-3a81-aa655ab4a523@intel.com \
    --to=fengwei.yin@intel.com \
    --cc=e@80x24.org \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).