From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>,
Peter Maydell <peter.maydell@linaro.org>,
Marcel Apfelbaum <marcel@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Update git URLs for my trees
Date: Tue, 12 Sep 2017 10:14:05 +0200 [thread overview]
Message-ID: <16c0d5ee-f132-42d2-4b69-ee67e99c2954@redhat.com> (raw)
In-Reply-To: <20170901154701.GO7570@localhost.localdomain>
On 01/09/2017 17:47, Eduardo Habkost wrote:
> On Fri, Sep 01, 2017 at 12:39:28PM -0300, Eduardo Habkost wrote:
>> List the branches where I queue patches for Machine Core, NUMA,
>> Memory Backends, and X86. Update the NUMA section to list the
>> "numa-next" branch instead of "numa".
>>
>> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>> ---
>> MAINTAINERS | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index ccee28b12d..d72d8183bf 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -250,6 +250,7 @@ S: Maintained
>> F: target/i386/
>> F: hw/i386/
>> F: disas/i386.c
>> +T: git git://github.com/ehabkost/qemu.git x86-next
>
> Note: in the case of X86, Paolo and Richard have their own trees
> too. We probably should list them to avoid misleading people to
> think mine is the only one.
>
> Paolo, Richard: any git URLs you would like to list here?
I don't have a public branch. Because I generally collect random
patches and send them out when I have time to test, the public branch
might not even compile at times. :)
Paolo
prev parent reply other threads:[~2017-09-12 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 15:39 [Qemu-devel] [PATCH] MAINTAINERS: Update git URLs for my trees Eduardo Habkost
2017-09-01 15:47 ` Eduardo Habkost
2017-09-01 16:51 ` Richard Henderson
2017-09-12 8:14 ` Paolo Bonzini [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=16c0d5ee-f132-42d2-4b69-ee67e99c2954@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).