All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Kamil Rytarowski <n54@gmx.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] maintainers: Add myself as a NetBSD reviewer
Date: Mon, 15 May 2017 16:43:41 +0200	[thread overview]
Message-ID: <296a3be1-ded2-2fd9-5ea2-86b1e786d5b7@redhat.com> (raw)
In-Reply-To: <b299b025-720c-f2c0-1d63-8baf9b96d8b5@gmx.com>



On 15/05/2017 16:22, Kamil Rytarowski wrote:
> On 15.05.2017 16:13, Stefan Hajnoczi wrote:
>> On Sat, May 13, 2017 at 04:21:43AM +0200, Kamil Rytarowski wrote:
>>> I volunteer to review NetBSD patches.
>>> Adding myself will help to not miss some of them.
>>>
>>> Restore NetBSD as a maintained host.
>>>
>>> All patches to make qemu/pkgsrc building have been emitted to review.
>>>
>>> Signed-off-by: Kamil Rytarowski <n54@gmx.com>
>>> ---
>>>  MAINTAINERS | 6 ++++++
>>>  configure   | 1 +
>>>  2 files changed, 7 insertions(+)
>>
>> Will you maintain a patch queue (git repo) so you can send pull
>> requests?  If yes, please add a T: field.
>>
> 
> I don't think that there is a need for an additional patch queue, at
> least in the maintained mode as a volunteer in spare time.
> 
> If there would be more BSD people, we could share a dedicated queue of
> patches.

How would patches be sent to the committer then?

Thanks,

Paolo

  reply	other threads:[~2017-05-15 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  2:21 [Qemu-devel] [PATCH] maintainers: Add myself as a NetBSD reviewer Kamil Rytarowski
2017-05-15 14:13 ` Stefan Hajnoczi
2017-05-15 14:22   ` Kamil Rytarowski
2017-05-15 14:43     ` Paolo Bonzini [this message]
2017-05-16 14:32       ` Stefan Hajnoczi
2017-05-16 14:35 ` Stefan Hajnoczi

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=296a3be1-ded2-2fd9-5ea2-86b1e786d5b7@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=n54@gmx.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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.