user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Salil Mehta <salil.mehta@huawei.com>,
	 "salil.mehta@opnsrc.net" <salil.mehta@opnsrc.net>,
	helpdesk@kernel.org, meta@public-inbox.org
Subject: Re: [Question] review links are disappearing from the qemu-devel mailing-list
Date: Mon, 6 Nov 2023 13:18:10 -0500	[thread overview]
Message-ID: <20231106-fabulous-merciful-oyster-96cede@meerkat> (raw)
In-Reply-To: <20231106113920-mutt-send-email-mst@kernel.org>

On Mon, Nov 06, 2023 at 11:49:02AM -0500, Michael S. Tsirkin wrote:
> > 2023-10-13 10:51 ` [PATCH V6 3/9] hw/acpi: Add ACPI CPU hotplug init stub Salil Mehta via
> >      [not found]   ` <20231027150536.3c481246@imammedo.users.ipa.redhat.com>---> why is this?

Unhelpfully, because the archiver address never received that, at least not
according to the logs.

I see that message-id being delivered to other subscribers with kernel.org
addresses, just never to the archiver.

Sorry I can't be more helpful.

-K

  parent reply	other threads:[~2023-11-06 18:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49f4357be7c4470fa1f0398e346c0173@huawei.com>
2023-11-06 16:49 ` [Question] review links are disappearing from the qemu-devel mailing-list Michael S. Tsirkin
2023-11-06 16:51   ` Michael S. Tsirkin
2023-11-06 17:36     ` Eric Wong
2023-11-07  9:54       ` Salil Mehta
2023-11-07  9:57         ` Michael S. Tsirkin
2023-11-07  9:50     ` Salil Mehta
2023-11-07 13:42       ` Igor Mammedov
2023-11-07 13:51         ` Michael S. Tsirkin
2023-11-08  9:30       ` Igor Mammedov
2023-11-08 10:04         ` Salil Mehta
2023-11-06 18:18   ` Konstantin Ryabitsev [this message]
2023-11-07  9:57     ` Salil Mehta
2023-11-07 13:56       ` Konstantin Ryabitsev
2023-11-07 14:14         ` Michael S. Tsirkin
2023-11-13 19:27           ` Salil Mehta
2023-11-13 19:32             ` Konstantin Ryabitsev
2023-11-13 19:39               ` Salil Mehta
2023-11-13 20:44                 ` Konstantin Ryabitsev
2023-11-13 22:26                   ` Salil Mehta
2023-11-14 11:03                     ` Salil Mehta
2023-11-14 15:10                       ` Konstantin Ryabitsev
2023-11-14 16:11                         ` Salil Mehta
2023-11-14 16:46                           ` Konstantin Ryabitsev
2023-11-14 15:32                       ` Eric Wong
2023-11-14 16:21                         ` Salil Mehta
2023-11-14 16:36                           ` Eric Wong
2023-11-14 16:59                             ` Konstantin Ryabitsev
2023-11-14 17:21                               ` Eric Wong
2023-11-14 17:25                               ` Salil Mehta
2023-11-15 11:14                                 ` Salil Mehta
2023-11-13 19:33             ` Salil Mehta
2023-11-07  9:46   ` Salil Mehta

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=20231106-fabulous-merciful-oyster-96cede@meerkat \
    --to=konstantin@linuxfoundation.org \
    --cc=helpdesk@kernel.org \
    --cc=meta@public-inbox.org \
    --cc=mst@redhat.com \
    --cc=salil.mehta@huawei.com \
    --cc=salil.mehta@opnsrc.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).