From: Peter Maydell <peter.maydell@linaro.org>
To: Jag Raman <jag.raman@oracle.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
John Johnson <john.g.johnson@oracle.com>,
David Hildenbrand <david@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Willian Rampazzo <willianr@redhat.com>,
David Hildenbrand <dhildenb@redhat.com>,
Cleber Rosa <crosa@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: tests/acceptance/multiprocess.py test failure
Date: Tue, 20 Jul 2021 21:20:33 +0100 [thread overview]
Message-ID: <CAFEAcA8jOf8-rojji7_z3-N10AeiynQ7NVv4aaMCZGL3npwpxg@mail.gmail.com> (raw)
In-Reply-To: <8D9638C2-D992-416E-9A92-58128F1001CB@oracle.com>
On Tue, 20 Jul 2021 at 21:18, Jag Raman <jag.raman@oracle.com> wrote:
>
>
>
> > On Jul 20, 2021, at 2:39 PM, Cleber Rosa <crosa@redhat.com> wrote:
> >
> >
> > Jag Raman writes:
> >>
> >> We presently don’t have permissions to send a PR to
> >> upstream (Peter Maydell).
> >>
> >> Presently, we are requesting someone else who has
> >> permissions to do PRs on our behalf. We will work
> >> on getting permissions to send PRs going forward.
> > I'm going to include that patch in an upcoming PR. Please let me know
> > if this is not what you intended.
> >
> > PS: I'm not sure I follow what your specific permission problem is, if
> > it's technical or something else. But, in either case, I'd recommend you
> > sync the MAINTAINERS file entries with your roles/abilities to maintain
> > those files listed.
> I have not registered a GPG keys to submit PR - please see following
> email for context:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg765788.html
>
> I’ll get started on this process as I can help with smaller patches.
This isn't a technical thing particularly -- I just prefer that
if you're not going to be submitting a lot of patches that they
go through some other submaintainer who can review and curate
them as they go past. I do not want us to have a structure
where we have 500 "submaintainers" all directly submitting PRs to me.
thanks
-- PMM
prev parent reply other threads:[~2021-07-20 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 1:59 tests/acceptance/multiprocess.py test failure Cleber Rosa
2021-07-15 8:16 ` David Hildenbrand
2021-07-15 13:16 ` Cleber Rosa
2021-07-15 14:51 ` Jag Raman
2021-07-20 18:39 ` Cleber Rosa
2021-07-20 20:13 ` Jag Raman
2021-07-20 20:20 ` Peter Maydell [this message]
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=CAFEAcA8jOf8-rojji7_z3-N10AeiynQ7NVv4aaMCZGL3npwpxg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=crosa@redhat.com \
--cc=david@redhat.com \
--cc=dhildenb@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=willianr@redhat.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).