From: "Daniel P. Berrange" <berrange@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel@nongnu.org, Fam Zheng <famz@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v8 0/6] Initial support for keycodemapdb GIT submodule
Date: Mon, 2 Oct 2017 11:55:37 +0100 [thread overview]
Message-ID: <20171002105537.GA9597@redhat.com> (raw)
In-Reply-To: <20171002091838.GC27086@redhat.com>
On Mon, Oct 02, 2017 at 10:18:38AM +0100, Daniel P. Berrange wrote:
> On Fri, Sep 29, 2017 at 05:29:53PM -0400, Programmingkid wrote:
> >
> > > On Sep 29, 2017, at 6:12 AM, qemu-devel-request@gnu.org wrote:
> > >
> > > Message: 15
> > > Date: Fri, 29 Sep 2017 11:11:55 +0100
> > > From: "Daniel P. Berrange" <berrange@redhat.com <mailto:berrange@redhat.com>>
> > > To: qemu-devel@nongnu.org <mailto:qemu-devel@nongnu.org>
> > > Cc: Fam Zheng <famz@redhat.com <mailto:famz@redhat.com>>, Gerd Hoffmann <kraxel@redhat.com <mailto:kraxel@redhat.com>>,
> > > Peter Maydell <peter.maydell@linaro.org <mailto:peter.maydell@linaro.org>>, Paolo Bonzini
> > > <pbonzini@redhat.com <mailto:pbonzini@redhat.com>>, "Daniel P. Berrange" <berrange@redhat.com <mailto:berrange@redhat.com>>
> > > Subject: [Qemu-devel] [PATCH v8 0/6] Initial support for keycodemapdb
> > > GIT submodule
> > > Message-ID: <20170929101201.21039-1-berrange@redhat.com <mailto:20170929101201.21039-1-berrange@redhat.com>>
> > >
> > > This patch series is an update to:
> > >
> > <snip>
> >
> > For some reason this patch series isn't showing up in your patchworks page:
> > https://patchwork.ozlabs.org/project/qemu-devel/list/?submitter=2694
>
> I dunno who maintains that service, but it is not showing *any* qemu-devel
> mail that has been sent since the list-id header changed from nongnu.org
> to gnu.org
Managed to track down an admin for patchwork and they fixed its list-id
filter, so it should start getting emails again. Unfortunately I think
any mails betwen Sept 28th and today will be lost from patchwork forever.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-10-02 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4848.1506679941.14747.qemu-devel@gnu.org>
[not found] ` <49B4FB8A-C439-4912-BD30-D4FECF709BB8@gmail.com>
2017-09-29 21:40 ` [Qemu-devel] [PATCH v8 0/6] Initial support for keycodemapdb GIT submodule Programmingkid
[not found] ` <20171002091838.GC27086@redhat.com>
2017-10-02 10:55 ` Daniel P. Berrange [this message]
[not found] <mailman.5237.1506939080.14747.qemu-devel@gnu.org>
2017-10-02 15:52 ` Programmingkid
2017-10-04 5:48 ` Fam Zheng
2017-10-04 14:09 ` Programmingkid
2017-09-29 10:11 Daniel P. Berrange
2017-10-02 9:56 ` Daniel P. Berrange
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171002105537.GA9597@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).