linux-kernel - Re: [GIT PULL] First batch of KVM changes for v4.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+55aFwg3t1F+032pHW3EfNLcG2omHsnkMTVorKESOjPyJNsFQ@mail.gmail.com>
Date:   Fri, 8 Sep 2017 15:25:58 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Radim Krčmář <rkrcmar@...hat.com>
Cc:     Paolo Bonzini <pbonzini@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        KVM list <kvm@...r.kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for v4.14

On Fri, Sep 8, 2017 at 7:30 AM, Radim Krčmář <rkrcmar@...hat.com> wrote:
>
>  Topic branch merges in s390 and powerpc
> are already in mainline -- would you prefer to see the expected result
> after merge instead of what `git request-pull` produces?

So generally, if you do the test-merge anyway (which I appreciate), I
generally prefer the expected results instead of the raw `git
request-pull` output.

But it's also definitely not a hard requirement.

Basically, the rough guidance is that "git request-pull is sufficient".

And if you are not a git power-user (ie you don't use lots of
branches, and there aren't any shared topic branches with other
trees), git request-pull will simply always be the right thing anyway.

For maintainers that _are_ doing fancier things with git, and are
sharing branches and doing their own complex git history, "git
request-pull" is the simple interface - and is generally _too_ simple.
So then I _hope_ (but do not require) that such maintainers will do
the test-merge anyway for other reasons, and take the diffstat from
that instead, since the simple "git request-pull" model won't
necessarily give the right diffstat for the more complex history case.

So it's appreciated, but not required.

          Linus