From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932785AbdC3Jkx (ORCPT ); Thu, 30 Mar 2017 05:40:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59528 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932348AbdC3Jkv (ORCPT ); Thu, 30 Mar 2017 05:40:51 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 3FD22C056800 Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx08.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=pbonzini@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 3FD22C056800 Subject: Re: linux-next: unsigned commits in the kvm tree To: Stephen Rothwell , Marcelo Tosatti , Gleb Natapov , KVM References: <20170330092142.4ec22c6a@canb.auug.org.au> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= From: Paolo Bonzini Message-ID: Date: Thu, 30 Mar 2017 11:40:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170330092142.4ec22c6a@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Thu, 30 Mar 2017 09:40:45 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. Paolo