From: Randy Dunlap <randy.dunlap@oracle.com>
To: Joe Perches <joe@perches.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
torvalds <torvalds@linux-foundation.org>,
akpm <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTTAINERS: update DCO info
Date: Wed, 22 Aug 2007 16:00:32 -0700 [thread overview]
Message-ID: <46CCC010.8070207@oracle.com> (raw)
In-Reply-To: <1187823476.24819.52.camel@localhost>
Joe Perches wrote:
> On Wed, 2007-08-22 at 08:24 -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <randy.dunlap@oracle.com>
>>
>> Update URL for DCO (old URL is invalid).
>> Also, point to SubmittingPatches for the current DCO.
>>
>> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
>> ---
>> MAINTAINERS | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> --- linux-2.6.23-rc3-git2.orig/MAINTAINERS
>> +++ linux-2.6.23-rc3-git2/MAINTAINERS
>> @@ -45,8 +45,11 @@ trivial patch so apply some common sense
>>
>> PLEASE remember that submissions must be made under the terms
>> of the OSDL certificate of contribution
>> - (http://www.osdl.org/newsroom/press_releases/2004/2004_05_24_dco.html)
>> + (http://old.linux-foundation.org/newsroom/press_releases/2004/2004_05_24_dco.html)
>> and should include a Signed-off-by: line.
>> + The current certificate is also documented in
>> + Documentation/SubmittingPatches as the Developer's Certificate
>> + of Origin (DCO).
>
> Why have an external link which may go out of date
> when we already have the cert?
>
> It's really short, we could just quote it.
I wouldn't bother repeating it, but I'll happily remove the URL
and just refer to Documentation/SubmittingPatches. I think that
the latter is a good place for it to stay.
> Maybe it should be a separate file
> Documentation/Developer_Certificate_of_Origin
> and referenced directly.
>
> Developer's Certificate of Origin 1.1
>
> 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.
>
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-08-22 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 15:24 [PATCH] MAINTTAINERS: update DCO info Randy Dunlap
2007-08-22 22:57 ` Joe Perches
2007-08-22 23:00 ` Randy Dunlap [this message]
2007-08-24 6:50 ` [PATCH v2] " Randy Dunlap
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=46CCC010.8070207@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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