From: Eduardo Otubo <eduardo.otubo@profitbricks.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: namnamc@safe-mail.net, Andrew Jones <drjones@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 00/04] seccomp branch queue
Date: Thu, 22 Oct 2015 12:14:22 +0200 [thread overview]
Message-ID: <20151022101422.GA7506@vader> (raw)
In-Reply-To: <CAFEAcA9CJcrz2GhraVfL7S+6b6eyb8nF1k08jx4d0P+KUJyBag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]
On Fri, Oct 16, 2015 at 05=12=18PM +0100, Peter Maydell wrote:
> On 15 October 2015 at 08:57, Eduardo Otubo
> <eduardo.otubo@profitbricks.com> wrote:
> > The following changes since commit c49d3411faae8ffaab8f7e5db47405a008411c10:
> >
> > Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2015-10-12' into staging (2015-10-13 10:42:06 +0100)
> >
> > are available in the git repository at:
> >
> > git://github.com/otubo/qemu.git tags/pull-seccomp-20151015
> >
> > for you to fetch changes up to d8e4d1ef78093037fc6483561aee3aaedebbaa37:
> >
> > Add syscalls for -runas and -chroot to the seccomp sandbox (2015-10-15 09:41:15 +0200)
> >
> > ----------------------------------------------------------------
> > seccomp branch queue
> >
> > ----------------------------------------------------------------
> > Andrew Jones (2):
> > libseccomp: add cacheflush to whitelist
> > configure: arm/aarch64: allow enable-seccomp
> >
> > Namsun Ch'o (2):
> > Add argument filters to the seccomp sandbox
> > Add syscalls for -runas and -chroot to the seccomp sandbox
>
> The commit messages in this are a bit of a mess. In particular,
> there's lots of chatty information about "I compiled QEMU and it worked fine"
> and "changes between v2 and v3" information, which should all
> go below the '---' divider so it doesn't appear in the final
> commit logs. "Add argument filters to the seccomp sandbox" should
> really also have a longer and more explanatory commit message
> giving rationale for the change, and so on, since it's adding
> a fair bit of new code.
>
> Can you either clean them up or ask the submitters to do so,
> please?
I guess this is addressed to Namsun's patches.
Namsun, can you rewrite the commit messages according to Peter's
suggestions and resend?
Thanks,
>
> thanks
> -- PMM
--
Eduardo Otubo
ProfitBricks GmbH
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-22 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 7:57 [Qemu-devel] [PULL 00/04] seccomp branch queue Eduardo Otubo
2015-10-15 7:57 ` [Qemu-devel] [PULL 01/04] libseccomp: add cacheflush to whitelist Eduardo Otubo
2015-10-15 7:57 ` [Qemu-devel] [PULL 02/04] configure: arm/aarch64: allow enable-seccomp Eduardo Otubo
2015-10-15 7:57 ` [Qemu-devel] [PULL 03/04] Add argument filters to the seccomp sandbox Eduardo Otubo
2015-10-15 7:58 ` [Qemu-devel] [PULL 04/04] Add syscalls for -runas and -chroot " Eduardo Otubo
2015-10-16 16:12 ` [Qemu-devel] [PULL 00/04] seccomp branch queue Peter Maydell
2015-10-22 10:14 ` Eduardo Otubo [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-18 7:22 Namsun Ch'o
2015-10-14 9:38 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=20151022101422.GA7506@vader \
--to=eduardo.otubo@profitbricks.com \
--cc=drjones@redhat.com \
--cc=namnamc@safe-mail.net \
--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 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.