From: Namsun Ch'o <namnamc@airmail.cc>
To: eduardo.otubo@profitbricks.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 04/05] seccomp: add setuid, setgid, chroot and setgroups to whitelist
Date: Thu, 19 Nov 2015 02:35:51 +0000 [thread overview]
Message-ID: <2f199822c33b7522df4f0ca3abfe7883@airmail.cc> (raw)
I have no idea why the lines didn't wrap in my last post... Sorry about
that.
next reply other threads:[~2015-11-19 2:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 2:35 Namsun Ch'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 7:10 [Qemu-devel] [PULL 04/05] seccomp: add setuid, setgid, chroot and setgroups to whitelist Namsun Ch'o
2015-10-30 13:44 [Qemu-devel] [PULL 00/05] seccomp branch queue Eduardo Otubo
2015-10-30 13:44 ` [Qemu-devel] [PULL 04/05] seccomp: add setuid, setgid, chroot and setgroups to whitelist Eduardo Otubo
2015-11-02 7:51 ` Paolo Bonzini
2015-11-11 8:25 ` Eduardo Otubo
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=2f199822c33b7522df4f0ca3abfe7883@airmail.cc \
--to=namnamc@airmail.cc \
--cc=c2b16793c88670d3ac3f4451cd6470ea@airmail.cc \
--cc=eduardo.otubo@profitbricks.com \
--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).