From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the powerpc tree
Date: Mon, 25 Feb 2019 09:47:25 +1100 [thread overview]
Message-ID: <20190225094659.741bf42f@canb.auug.org.au> (raw)
In-Reply-To: <8736odl846.fsf@concordia.ellerman.id.au>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
Hi Michael,
On Sun, 24 Feb 2019 22:48:57 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> But do they need SOBs?
I think so, since they modify the code ..
> The DCO says:
>
> By making a contribution to this project, I certify that:
>
> (a) The contribution was created in whole or in part by me and I
> have the right to submit it under the open source license
> indicated in the file; or
>
> (b) The contribution is based upon previous work that, to the best
> of my knowledge, is covered under an appropriate open source
> license and I have the right under that license to submit that
> work with modifications, whether created in whole or in part
> by me, under the same open source license (unless I am
> permitted to submit under a different license), as indicated
> in the file; or
>
> (c) The contribution was provided directly to me by some other
> person who certified (a), (b) or (c) and I have not modified
> it.
>
> (d) I understand and agree that this project and the contribution
> are public and that a record of the contribution (including all
> personal information I submit with it, including my sign-off) is
> maintained indefinitely and may be redistributed consistent with
> this project or the open source license(s) involved.
>
>
> Only d) really applies to a revert, and as the maintainer I feel like d)
> is kind of implied.
I read this as (a || b || c) && d. And if there is no SOB, then none
of the above is certified.
> Anyway I'll try and remember to do it in future if that's The Rule ;)
Its just as effective as the rest of our rules ... i.e. a strong
suggestion :-)
Thanks
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-02-24 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 14:05 linux-next: Signed-off-by missing for commit in the powerpc tree Stephen Rothwell
2019-02-24 11:48 ` Michael Ellerman
2019-02-24 22:47 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 21:16 Stephen Rothwell
2023-10-24 3:57 ` Michael Ellerman
2022-05-19 22:31 Stephen Rothwell
2022-05-20 5:20 ` Nicholas Piggin
2021-06-21 21:46 Stephen Rothwell
2021-06-24 7:42 ` Michael Ellerman
2019-05-06 20:35 Stephen Rothwell
2018-06-03 18:26 Stephen Rothwell
2018-06-04 10:39 ` Michael Ellerman
2017-11-14 20:26 Stephen Rothwell
2017-11-15 10:11 ` Michael Ellerman
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=20190225094659.741bf42f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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;
as well as URLs for NNTP newsgroup(s).