linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Marcelo Tosatti" <mtosatti@redhat.com>,
	"Gleb Natapov" <gleb@kernel.org>, KVM <kvm@vger.kernel.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: linux-next: unsigned commits in the kvm tree
Date: Thu, 30 Mar 2017 22:01:06 +1100	[thread overview]
Message-ID: <20170330220106.5e96f825@canb.auug.org.au> (raw)
In-Reply-To: <e118215b-0a44-e1d7-c665-41112a44df0a@redhat.com>

Hi Paolo,

On Thu, 30 Mar 2017 11:40:41 +0200 Paolo Bonzini <pbonzini@redhat.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

      reply	other threads:[~2017-03-30 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 22:21 linux-next: unsigned commits in the kvm tree Stephen Rothwell
2017-03-30  9:40 ` Paolo Bonzini
2017-03-30 11:01   ` Stephen Rothwell [this message]

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=20170330220106.5e96f825@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).