From: Markus Armbruster <armbru@redhat.com>
To: Namsun Ch'o <namnamc@Safe-mail.net>
Cc: pmoore@redhat.com, qemu-devel@nongnu.org, eduardo.otubo@profitbricks.com
Subject: Re: [Qemu-devel] [PATCH v2] Add argument filters to the seccomp sandbox
Date: Thu, 01 Oct 2015 07:58:58 +0200 [thread overview]
Message-ID: <871tdfnn8d.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <N1-Erq2qAg2mx@Safe-mail.net> (Namsun Ch'o's message of "Wed, 30 Sep 2015 02:41:52 -0400")
"Namsun Ch'o" <namnamc@Safe-mail.net> writes:
>> (I'm not sure what happens to your emails that all of them does not
>> relate to the same thread/Message-ID, making a pain to follow through
>> out the volume of email on the list, please pay attention to that)
>
> I just click Reply All, I'm not sure how else I would do it. Are they somehow
> being posted as new top level threads instead of replies?
This message lacks In-Reply-To: and References: headers. Whatever you
use to send e-mail seems grossly deficient. Perhaps it has some "don't
be such an ass" configuration button, but I doubt it.
[...]
next prev parent reply other threads:[~2015-10-01 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 6:41 [Qemu-devel] [PATCH v2] Add argument filters to the seccomp sandbox Namsun Ch'o
2015-10-01 5:58 ` Markus Armbruster [this message]
[not found] <d55ad1eed872006f0634c3e0067553a5@airmail.cc>
2015-10-01 7:17 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2015-09-29 3:14 Namsun Ch'o
2015-09-29 15:38 ` Eduardo Otubo
2015-09-29 22:12 ` Paul Moore
2015-09-28 21:34 Namsun Ch'o
2015-09-29 1:19 ` Paul Moore
2015-09-26 5:06 Namsun Ch'o
2015-09-28 18:24 ` Paul Moore
2015-09-25 4:53 Namsun Ch'o
2015-09-25 17:03 ` Paul Moore
2015-09-11 0:54 namnamc
2015-09-24 9:59 ` 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=871tdfnn8d.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=namnamc@Safe-mail.net \
--cc=pmoore@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.