linux-kernel - Re: linux-next: unsigned commits in the kvm tree

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: <20170330220106.5e96f825@canb.auug.org.au>
Date:   Thu, 30 Mar 2017 22:01:06 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Marcelo Tosatti <mtosatti@...hat.com>,
        Gleb Natapov <gleb@...nel.org>, KVM <kvm@...r.kernel.org>,
        linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Radim Krčmář <rkrcmar@...hat.com>
Subject: Re: linux-next: unsigned commits in the kvm tree

Hi Paolo,

On Thu, 30 Mar 2017 11:40:41 +0200 Paolo Bonzini <pbonzini@...hat.com> wrote:
>
> On 30/03/2017 00:21, Stephen Rothwell wrote:
> > 
> > I noticed that several commits in the kvm tree
> > (git://git.kernel.org/pub/scm/virt/kvm/kvm.git#linux-next) today have
> > no Signed-off-by for their committer :-(  
> 
> Hmm, that must have happened because I rebased them before (testing and)
> pushing to kvm/next; kvm/next does not rebase but kvm/queue does.
> 
> Still, it's weird because I have done that many times and it's the first
> time you noticed.  Do you have scripts for that or did you just happen
> to notice?  Or maybe there is a difference in what "git rebase" vs. "git
> rebase -i" does to the committer email, or something obscure like that.

I should write a script, but at the moment I just notice sometimes.  I
have a quick look at what is new in each tree each morning and
sometimes things stick out :-)
-- 
Cheers,
Stephen Rothwell