qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/04] seccomp branch queue


From: Eduardo Otubo
Subject: Re: [Qemu-devel] [PULL 00/04] seccomp branch queue
Date: Thu, 22 Oct 2015 12:14:22 +0200
User-agent: Mutt/1.5.23 (2014-03-12)

On Fri, Oct 16, 2015 at 05=12=18PM +0100, Peter Maydell wrote:
> On 15 October 2015 at 08:57, Eduardo Otubo
> <address@hidden> 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: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]