From: James Bottomley <James.Bottomley@HansenPartnership•com>
To: "Martin K. Petersen" <martin.petersen@oracle•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commits in the scsi tree
Date: Wed, 09 Aug 2017 09:32:47 -0700 [thread overview]
Message-ID: <1502296367.3602.26.camel@HansenPartnership.com> (raw)
In-Reply-To: <yq14ltg676h.fsf@oracle.com>
On Wed, 2017-08-09 at 12:24 -0400, Martin K. Petersen wrote:
> James,
>
> >
> > Yes we had to drop a commit which proved problematic in the fixes
> > tree.
>
> I'm still not sure why you decided to rebase instead of waiting for
> me to drop the patch. That's how we usually do it...
We can certainly do it that way around. If you want to rebase to drop
the patch, I can set the top of the fixes tree to your rebase.
James
prev parent reply other threads:[~2017-08-09 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 23:27 linux-next: Signed-off-by missing for commits in the scsi tree Stephen Rothwell
2017-08-08 23:41 ` James Bottomley
2017-08-08 23:53 ` Stephen Rothwell
2017-08-09 16:24 ` Martin K. Petersen
2017-08-09 16:32 ` James Bottomley [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=1502296367.3602.26.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=martin.petersen@oracle$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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