From: Richard Henderson <richard.henderson@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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: Fri, 1 Sep 2017 09:51:26 -0700 [thread overview]
Message-ID: <32b34780-ecaf-9d2d-60a8-5cb3f6ec0a00@linaro.org> (raw)
In-Reply-To: <20170901154701.GO7570@localhost.localdomain>
On 09/01/2017 08:47 AM, Eduardo Habkost wrote:
> Paolo, Richard: any git URLs you would like to list here?
I don't have a fixed branch name for my target/i386 development.
r~
next prev parent reply other threads:[~2017-09-01 16:51 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 [this message]
2017-09-12 8:14 ` Paolo Bonzini
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=32b34780-ecaf-9d2d-60a8-5cb3f6ec0a00@linaro.org \
--to=richard.henderson@linaro.org \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).