From: Eric Blake <eblake@redhat.com>
To: Sunil Muthuswamy <sunilmut@microsoft.com>,
Paolo Bonzini <bonzini@gnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: qemu repo lockdown message for a WHPX PR
Date: Wed, 29 Jul 2020 15:18:45 -0500 [thread overview]
Message-ID: <4164d89a-9009-2ee3-3dc4-da3edeff4ab7@redhat.com> (raw)
In-Reply-To: <SN4PR2101MB088065186D10AC74BE9721BDC0700@SN4PR2101MB0880.namprd21.prod.outlook.com>
On 7/29/20 3:05 PM, Sunil Muthuswamy wrote:
> Adding Peter Maydell as well.
>
>> -----Original Message-----
>> From: Sunil Muthuswamy
>> Sent: Tuesday, July 28, 2020 12:20 PM
>> To: Paolo Bonzini <bonzini@gnu.org>
>> Cc: qemu-devel@nongnu.org
>> Subject: qemu repo lockdown message for a WHPX PR
>>
>> Hey Paolo,
>>
>> Following your suggestion of creating PRs for WHPX changes, I tried creating a PR https://github.com/qemu/qemu/pull/95
>>
>> But, I am getting repo-lockdown message. What do I need to do differently?
Are you trying to submit a patch? If so, we prefer submissions to the
mailing list rather than via github pull requests:
https://wiki.qemu.org/Contribute/SubmitAPatch
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2020-07-29 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 19:19 qemu repo lockdown message for a WHPX PR Sunil Muthuswamy
2020-07-29 20:05 ` Sunil Muthuswamy
2020-07-29 20:18 ` Eric Blake [this message]
2020-07-29 20:24 ` [EXTERNAL] " Sunil Muthuswamy
2020-07-29 20:28 ` Paolo Bonzini
2020-07-29 21:05 ` Peter Maydell
2020-07-30 21:53 ` [EXTERNAL] " Sunil Muthuswamy
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=4164d89a-9009-2ee3-3dc4-da3edeff4ab7@redhat.com \
--to=eblake@redhat.com \
--cc=bonzini@gnu.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sunilmut@microsoft.com \
/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).