From: Samuel Thibault <samuel.thibault@gnu.org>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@siemens.com, thuth@redhat.com, jasowang@redhat.com,
armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3 2/2] slirp: Allow disabling IPv4 or IPv6
Date: Fri, 25 Mar 2016 00:27:58 +0100 [thread overview]
Message-ID: <20160324232758.GQ2957@var.home> (raw)
In-Reply-To: <1458861955-11200-3-git-send-email-samuel.thibault@ens-lyon.org>
Samuel Thibault, on Fri 25 Mar 2016 00:25:55 +0100, wrote:
> Also rename recently-added options to make the whole coherent before 2.6
> gets released.
GRaaAH
I'm so motivated by such bike-shedding changes that I forgot to rework
the changelog.
Let me do that yet again.
Samuel
prev parent reply other threads:[~2016-03-24 23:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 23:25 [Qemu-devel] [PATCHv3 0/2] Rework ipv6 options, add ipv4/ipv6 enabling/disabling options Samuel Thibault
2016-03-24 23:25 ` [Qemu-devel] [PATCHv3 1/2] Rework ipv6 options Samuel Thibault
2016-03-24 23:25 ` [Qemu-devel] [PATCHv3 2/2] slirp: Allow disabling IPv4 or IPv6 Samuel Thibault
2016-03-24 23:27 ` Samuel Thibault [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=20160324232758.GQ2957@var.home \
--to=samuel.thibault@gnu.org \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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).