From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Sagi Grimberg" <sagi@grimberg.me>,
"Arnav Dawn" <a.dawn@samsung.com>,
"Guan Junxiong" <guanjunxiong@huawei.com>,
"Max Gurtovoy" <maxg@mellanox.com>,
"James Smart" <james.smart@broadcom.com>,
"Martin Wilck" <mwilck@suse.com>,
"Jan H. Schönherr" <jschoenh@amazon.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Philipp Reisner" <philipp.reisner@linbit.com>,
"Lars Ellenberg" <lars.ellenberg@linbit.com>,
"Roland Kammerer" <roland.kammerer@linbit.com>
Subject: Re: linux-next: Signed-off-bys missing for commits in the block tree
Date: Wed, 30 Aug 2017 20:13:02 +0200 [thread overview]
Message-ID: <20170830181302.GA5734@lst.de> (raw)
In-Reply-To: <20170831033400.423f0e6b@canb.auug.org.au>
On Thu, Aug 31, 2017 at 03:38:03AM +1000, Stephen Rothwell wrote:
> > I would say that if you rebase someone's commit(s), then you are on the
> > "patch's delivery path" and so should add a Signed-off-by tag.
>
> Yeah, I agree. Rebasing really is pretty much the exact same thing as
> applying a patch."
Ok, we'll get it right next time.
prev parent reply other threads:[~2017-08-30 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 17:06 linux-next: Signed-off-bys missing for commits in the block tree Stephen Rothwell
2017-08-30 17:09 ` Christoph Hellwig
2017-08-30 17:34 ` Stephen Rothwell
2017-08-30 18:13 ` Christoph Hellwig [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=20170830181302.GA5734@lst.de \
--to=hch@lst.de \
--cc=a.dawn@samsung.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=guanjunxiong@huawei.com \
--cc=james.smart@broadcom.com \
--cc=jschoenh@amazon.de \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=maxg@mellanox.com \
--cc=mwilck@suse.com \
--cc=philipp.reisner@linbit.com \
--cc=roland.kammerer@linbit.com \
--cc=sagi@grimberg.me \
--cc=sfr@canb.auug.org.au \
/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