From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Joe Perches <joe@perches.com>,
torvalds <torvalds@linux-foundation.org>,
akpm <akpm@linux-foundation.org>
Subject: [PATCH v2] MAINTTAINERS: update DCO info
Date: Thu, 23 Aug 2007 23:50:43 -0700 [thread overview]
Message-ID: <20070823235043.ff1c5484.randy.dunlap@oracle.com> (raw)
In-Reply-To: <46CCC010.8070207@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Drop the URL for DCO (URL is invalid).
Also, point to SubmittingPatches for the current DCO.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
MAINTAINERS | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--- linux-2.6.23-rc3-git6.orig/MAINTAINERS
+++ linux-2.6.23-rc3-git6/MAINTAINERS
@@ -44,9 +44,10 @@ trivial patch so apply some common sense
or does something very odd once a month document it.
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)
- and should include a Signed-off-by: line.
+ of the OSDL certificate of contribution and should include a
+ Signed-off-by: line. The current version of this "Developer's
+ Certificate of Origin" (DCO) is listed in the file
+ Documentation/SubmittingPatches.
6. Make sure you have the right to send any changes you make. If you
do changes at work you may find your employer owns the patch
prev parent reply other threads:[~2007-08-24 6:52 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
2007-08-24 6:50 ` Randy Dunlap [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=20070823235043.ff1c5484.randy.dunlap@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