From: Konstantin Kostiuk <kkostiuk@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PULL 0/9] qemu-ga-win patches
Date: Sun, 16 Jan 2022 00:13:28 +0200 [thread overview]
Message-ID: <CAPMcbCrCSct7AEPgmPJ2qC+VQQGJcAqsJGJh4G0aS8mj4dRzSw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_fgs1JAjMDXjd76xFWfmTMba1BfhYHFPrXCQyUk6o-eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
On Sat, Jan 15, 2022 at 2:40 PM Peter Maydell <peter.maydell@linaro.org>
wrote:
> On Mon, 10 Jan 2022 at 13:46, Konstantin Kostiuk <kkostiuk@redhat.com>
> wrote:
> >
> > The following changes since commit
> df722e33d5da26ea8604500ca8f509245a0ea524:
> >
> > Merge tag 'bsd-user-arm-pull-request' of gitlab.com:bsdimp/qemu into
> staging (2022-01-08 09:37:59 -0800)
> >
> > are available in the Git repository at:
> >
> > https://github.com/kostyanf14/qemu.git tags/qga-win32-pull-2022-01-10
> >
> > for you to fetch changes up to 206ce9699fae1f631ac74b7e1115db2affc759fd:
> >
> > qga-win: Detect Windows 11 by build number (2022-01-10 13:05:25 +0000)
>
> Hi; this tag doesn't seem to be gpg-signed. QEMU only alloows pullreqs
> which are for gpg-signed tags, so you'll need to sign it. Please make
> sure you've uploaded your gpg key to a suitable keyserver (eg
> keyserver.ubuntu.com and/or keys.openpgp.org) and let me know which
> one so I can download it. If you can arrange to get your key signed by
> some of your RedHat colleagues (and upload the key with those signatures)
> that would also be helpful.
>
> thanks
> -- PMM
>
Hi. I uploaded my GPG key to keys.openpgp.org. You can find it by my RedHat
email.
Unfortunately, for now, this key can not be signed by other RedHat
developers.
I signed my tag and pushed it to GitHub. Should I resend this set of
patches?
For tag signing, I use the 'git tag -s' command.
I am sorry for the mistakes, this is my first PR.
Best Regards,
Konstantin Kostiuk.
[-- Attachment #2: Type: text/html, Size: 2445 bytes --]
next prev parent reply other threads:[~2022-01-15 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 13:46 [PULL 0/9] qemu-ga-win patches Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 1/9] MAINTAINERS: Add entry for QEMU Guest Agent Windows components Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 2/9] gqa-win: get_pci_info: Clean dev_info if handle is valid Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 3/9] gqa-win: get_pci_info: Use common 'end' label Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 4/9] gqa-win: get_pci_info: Free parent_dev_info properly Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 5/9] gqa-win: get_pci_info: Split logic to separate functions Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 6/9] gqa-win: get_pci_info: Add g_autofree for few variables Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 7/9] gqa-win: get_pci_info: Replace 'while' with 2 calls of the function Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 8/9] qga-win: Detect OS based on Windows 10 by first build number Konstantin Kostiuk
2022-01-10 13:46 ` [PULL 9/9] qga-win: Detect Windows 11 by " Konstantin Kostiuk
2022-01-10 14:14 ` [PULL 0/9] qemu-ga-win patches Philippe Mathieu-Daudé
2022-01-10 14:16 ` Peter Maydell
2022-01-10 14:37 ` Konstantin Kostiuk
2022-01-15 12:40 ` Peter Maydell
2022-01-15 22:13 ` Konstantin Kostiuk [this message]
2022-01-16 20:11 ` Peter Maydell
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=CAPMcbCrCSct7AEPgmPJ2qC+VQQGJcAqsJGJh4G0aS8mj4dRzSw@mail.gmail.com \
--to=kkostiuk@redhat.com \
--cc=peter.maydell@linaro.org \
--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).