From: Eric Blake <eblake@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Samuel Thibault <samuel.thibault@gnu.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form
Date: Tue, 15 May 2018 09:30:17 -0500 [thread overview]
Message-ID: <ad86c974-120e-4a2d-1db9-03d1b8ace247@redhat.com> (raw)
In-Reply-To: <87d13bdd-4a33-fb05-0c7c-36aabbd3d038@ozlabs.ru>
On 05/14/2018 02:00 AM, Alexey Kardashevskiy wrote:
> On 13/3/18 6:44 pm, Samuel Thibault wrote:
>> Alexey Kardashevskiy, on mar. 13 mars 2018 15:49:44 +1100, wrote:
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>
>> Applied to my tree, thanks!
>
>
> And what is your tree, is this something to be merged sometime later
> somewhere? :)
Per MAINTAINERS:
SLIRP
M: Samuel Thibault <samuel.thibault@ens-lyon.org>
M: Jan Kiszka <jan.kiszka@siemens.com>
S: Maintained
F: slirp/
F: net/slirp.c
F: include/net/slirp.h
T: git git://git.kiszka.org/qemu.git queues/slirp
which shows Jan's staging tree, but not Samuel's.
It's not a requirement for a maintainer to have a public-facing staging
tree, but many of them do, as it gives you a chance to test that what
will later be in a pull request matches what you expect.
At any rate,
https://wiki.qemu.org/Contribute/SubmitAPatch#Is_my_patch_in.3F mentions
that maintainers will batch together various related patches and send a
pull request for inclusion in the main repository, thus even when a
patch has been reviewed and staged, it may be another week or two before
it lands in mainline. Yes, it can feel slow, but in general it works
out for the best (as we have more chances to flag potential problems
before they affect everyone by being in mainline).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-05-15 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 4:49 [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form Alexey Kardashevskiy
2018-03-13 7:44 ` Samuel Thibault
2018-05-14 7:00 ` Alexey Kardashevskiy
2018-05-14 7:05 ` Samuel Thibault
2018-05-15 14:30 ` Eric Blake [this message]
2018-05-16 3:00 ` Alexey Kardashevskiy
2018-03-13 8:10 ` no-reply
2018-03-13 16:25 ` Eric Blake
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=ad86c974-120e-4a2d-1db9-03d1b8ace247@redhat.com \
--to=eblake@redhat.com \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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).