user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Salil Mehta <salil.mehta@huawei.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	Eric Wong <e@80x24.org>
Cc: Salil Mehta <salil.mehta@opnsrc.net>,
	"Michael S. Tsirkin" <mtsirkin@redhat.com>,
	"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: Wed, 15 Nov 2023 11:14:26 +0000	[thread overview]
Message-ID: <1b3d9492df654da2a821c2e4b1dd9177@huawei.com> (raw)
In-Reply-To: <c651b954a3fb47daa5953500f5db379a@huawei.com>

Hi Konstantin,

> From: Salil Mehta
> Sent: Tuesday, November 14, 2023 5:25 PM
> To: 'Konstantin Ryabitsev' <konstantin@linuxfoundation.org>; Eric Wong <e@80x24.org>
> 
> Hi Konstantin,
> 
> > From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
> > Sent: Tuesday, November 14, 2023 4:59 PM
> > To: Eric Wong <e@80x24.org>
> >
> > On Tue, Nov 14, 2023 at 04:36:29PM +0000, Eric Wong wrote:
> > > In any case, kernel.org folks should be able to import missing
> > > messages from GNU.org idempotently into lore/qemu-devel without
> > > having to resend:
> > >
> > > https://lists.gnu.org/archive/mbox/qemu-devel/2023-10
> > > https://lists.gnu.org/archive/mbox/qemu-devel/2023-11
> >
> > Just so this conversation is over, I've fed 2023-10 to the archive and the
> > links should be working now.
> >
> > But to make it clear, these messages didn't "disappear" from the archives.
> > They were never there because, for whatever reason, we never received them.
> 
> Many thanks for this help. I appreciate this.
> 
> Some has changed within the links but they are still not opening. I'll wait
> till tomorrow before checking it again.

I can confirm that all links have been restored and are visible again.

Many thanks for taking pains and helping to resolve this. Really appreciate this.


Best regards
Salil.


  reply	other threads:[~2023-11-15 11:14 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 [this message]
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=1b3d9492df654da2a821c2e4b1dd9177@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.
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).