All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cleber Rosa <crosa@redhat.com>
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>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: tests/acceptance/multiprocess.py test failure
Date: Tue, 20 Jul 2021 14:39:54 -0400	[thread overview]
Message-ID: <87o8aw3k3p.fsf@p50.localhost.localdomain> (raw)
In-Reply-To: <418D3B29-010B-4B5B-A310-F3E3DA110DA9@oracle.com>


Jag Raman writes:

>
> Hi Cleber,
>
> 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.
>
> Thank you!

Hi Jag,

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.

Best Regards,
- Cleber.



  reply	other threads:[~2021-07-20 18:41 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 [this message]
2021-07-20 20:13         ` Jag Raman
2021-07-20 20:20           ` 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=87o8aw3k3p.fsf@p50.localhost.localdomain \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.