unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Salil Mehta <salil.mehta@huawei.com>
To: Salil Mehta <salil.mehta@opnsrc.net>,
	"Michael S. Tsirkin" <mtsirkin@redhat.com>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "helpdesk@kernel.org" <helpdesk@kernel.org>,
	"meta@public-inbox.org" <meta@public-inbox.org>,
	Igor Mammedov <imammedo@redhat.com>
Subject: RE: [Question] review links are disappearing from the qemu-devel mailing-list
Date: Mon, 13 Nov 2023 19:33:29 +0000	[thread overview]
Message-ID: <f44232b2fe08433aa1adb1bbb99db35f@huawei.com> (raw)
In-Reply-To: <64d76631-15f1-4d5b-fd0e-685e06731f8d@opnsrc.net>

[-- Attachment #1: Type: text/plain, Size: 2825 bytes --]

Hi Michael,

> From: Salil Mehta <salil.mehta@opnsrc.net>
> Sent: Monday, November 13, 2023 7:28 PM
> To: Michael S. Tsirkin <mtsirkin@redhat.com>; Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> 
> Hi Michael,
> 
> On 07/11/2023 14:14, Michael S. Tsirkin wrote:
> > On Tue, Nov 07, 2023 at 08:56:01AM -0500, Konstantin Ryabitsev wrote:
> >> On Tue, Nov 07, 2023 at 09:57:55AM +0000, Salil Mehta wrote:
> >>>> 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.
> >>>
> >>> I can assure you that I saw these links present and working last Tuesday
> >>> and as mentioned earlier I did had an internal discussion using these links
> >>> as well. They have disappeared in between.
> >>
> >> Sorry, but this is not possible short of someone running a very specific
> >> command on lore (as administrator) to actually rewrite git history in the
> >> underlying repo. We only do this for GDPR requests or to remove
> >> illegal/abusive messages.
> >>
> >> E.g. these are all the messages we have in that repo from Igor:
> >> https://erol.kernel.org/qemu-devel/git/2/log/?qt=author&q=mammedov
> >>
> >> -K
> >
> > I just bounced that email again and now it's there.
> > Let everyone know if you see this again.
> 
> I am able to open [Patch V6 1/9] from outside the company network (as
> you can see the by [2] [3]) but strangely not from inside the company
> network. It purges below error from company network. I am totally stumped.
> 
> Message-Id <20231027145652.44cc845c@imammedo.users.ipa.redhat.com> 
> not found
> 
> Perhaps try an external site:
> [...]

Please check attachment of the complete error message from within the
company network.

Attachment: _20231027145652.44cc845c@imammedo.users.ipa.redhat.com_ not found.pdf



Thanks
Salil.
> 
> 
> Links for Igor's comment on [Patch V6 3/9, 4/9, 5/9, 7/9] are not
> working either from outside or from inside the company network.
> 
> 
> Attachments With This Mail:
> 1. [PATCH V6 0_9] Add architecture agnostic code to support vCPU Hotplug
>   - Salil Mehta via.pdf
> 
> 2. Re_ [PATCH V6 1_9] accel_kvm_ Extract common KVM vCPU
> {creation,parking} code - Igor Mammedov.eml
> 
> 3. Re_ [PATCH V6 1_9] accel_kvm_ Extract common KVM vCPU
> {creation,parking} code - Igor Mammedov.pdf
> 
> 
> Best regards
> Salil.

[-- Attachment #2: _20231027145652.44cc845c@imammedo.users.ipa.redhat.com_ not found.pdf --]
[-- Type: application/pdf, Size: 64768 bytes --]

  parent reply	other threads:[~2023-11-13 19:33 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
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 [this message]
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=f44232b2fe08433aa1adb1bbb99db35f@huawei.com \
    --to=salil.mehta@huawei.com \
    --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).