From: domen@coderock.org
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
domen@coderock.org
Subject: [patch 4/4] DCO: use IANA-reserved second level domain name
Date: Mon, 20 Jun 2005 23:57:22 +0200 [thread overview]
Message-ID: <20050620215722.845793000@nd47.coderock.org> (raw)
[-- Attachment #1: dco-Documentation_SubmittingPatches --]
[-- Type: text/plain, Size: 789 bytes --]
From: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
SubmittingPatches | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: quilt/Documentation/SubmittingPatches
===================================================================
--- quilt.orig/Documentation/SubmittingPatches
+++ quilt/Documentation/SubmittingPatches
@@ -299,7 +299,7 @@ can certify the below:
then you just add a line saying
- Signed-off-by: Random J Developer <random@developer.org>
+ Signed-off-by: Random J Developer <random@developer.example.org>
Some people also put extra tags at the end. They'll just be ignored for
now, but you can do this to mark internal company procedures or just
--
reply other threads:[~2005-06-20 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050620215722.845793000@nd47.coderock.org \
--to=domen@coderock.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.