unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Salil Mehta <salil.mehta@huawei.com>
To: Eric Wong <e@80x24.org>, "Michael S. Tsirkin" <mtsirkin@redhat.com>
Cc: "salil.mehta@opnsrc.net" <salil.mehta@opnsrc.net>,
	"helpdesk@kernel.org" <helpdesk@kernel.org>,
	"meta@public-inbox.org" <meta@public-inbox.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: RE: [Question] review links are disappearing from the qemu-devel mailing-list
Date: Tue, 7 Nov 2023 09:54:40 +0000	[thread overview]
Message-ID: <88d9d4ec99e64cdb98c856dab47f1e53@huawei.com> (raw)
In-Reply-To: <20231106173642.M163530@dcvr>

Hi Eric,

> From: Eric Wong <e@80x24.org>
> Sent: Monday, November 6, 2023 5:37 PM
> To: Michael S. Tsirkin <mtsirkin@redhat.com>
> 
> "Michael S. Tsirkin" <mtsirkin@redhat.com> wrote:
> > On Mon, Nov 06, 2023 at 11:49:06AM -0500, Michael S. Tsirkin wrote:
> > > On Mon, Nov 06, 2023 at 02:58:18PM +0000, Salil Mehta wrote:
> > > > Hi Michael,
> > > > I have noticed something very strange. Review links have been disappearing from the
> > > > Qemu-devel mailing list. For example, please jump to the thread overview present at
> > > > the last of this mailing thread of vCPU Hotplug.
> > > >
> > > > https://lore.kernel.org/qemu-devel/20231013105129.25648-1-salil.mehta@huawei.com/#r
> > > >
> > > > Some of the reviews done by Igor have simply disappeared from it.
> > > >
> > > > This one:
> > > > 2023-10-13 10:51 ` https://lore.kernel.org/qemu-devel/20231013105129.25648-2-salil.mehta@huawei.com/ Salil Mehta via
> > > >      [not found]   ` <https://lore.kernel.org/qemu-devel/20231027145652.44cc845c@imammedo.users.ipa.redhat.com/> ---> Why is this?
> > > >
> > > > And this one:
> > > > 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?
> > > > 2023-11-06 14:40     ` Salil Mehta via
> > > >
> > > >
> > > >
> > > > Any reasons you can think of or any leads you can give about whom should
> > > > I contact for these kind of issues. Who is the maintainer of qemu-devel
> > > > list?
> > > >
> > > >
> > > > Best regards
> > > > Salil.
> > > >
> > >
> > > I see the message here:
> > > https://lists.gnu.org/archive/html/qemu-devel/2023-10/msg09526.html
> > >
> > > so it only disappeared from lore.kernel.org
> > >
> > > Not 100% sure who to ask about it - Cc kernel.org/public-inbox devs and Konstantin who might know.
> > >
> > > Thanks!
> > >
> >
> > Also - it looks like I should have been CC'd on this but I did not get
> > a copy either. So something strange about this mail then? But gnu.org
> > archive was able to recover.
> >
> > Cc also Igor who sent this message - Igor could you attach a copy
> > of the original?
> >
> > Thanks!
> 
> FWIW, GNU has the mboxo||mboxrd file here:
> https://lists.gnu.org/archive/mbox/qemu-devel/2023-10
> 
> Looking at the raw message of
> <20231027150536.3c481246@imammedo.users.ipa.redhat.com>
> didn't reveal any obvious problems (HTML, spammy terms)
> 
> So I'm not sure why it didn't get into lore...

Surprisingly, I did see these links present and working last Tuesday
and in fact I did had an internal discussion using these links as well.
So they were definitely there.





  reply	other threads:[~2023-11-07  9:54 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 [this message]
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
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=88d9d4ec99e64cdb98c856dab47f1e53@huawei.com \
    --to=salil.mehta@huawei.com \
    --cc=e@80x24.org \
    --cc=helpdesk@kernel.org \
    --cc=imammedo@redhat.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.org \
    --cc=mtsirkin@redhat.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.
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).