From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] Formalize the meaning of Signed-off-by
Date: Thu, 28 Feb 2013 11:34:37 +0100 [thread overview]
Message-ID: <1362047677-29294-1-git-send-email-u.kleine-koenig@pengutronix.de> (raw)
Up to now Signed-off-by was not formalized so I doubt it has had any
significance. This patch makes the Linux Kernel's rules explicit (by
borrowing even the wording from it).
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
README.devel | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 55 insertions(+)
create mode 100644 README.devel
diff --git a/README.devel b/README.devel
new file mode 100644
index 0000000..028fb73
--- /dev/null
+++ b/README.devel
@@ -0,0 +1,55 @@
+PTXdist development
+===================
+
+Development Tree
+----------------
+
+PTXdist uses git for version control. The master repository is available at
+
+ git://git.pengutronix.de/git/ptxdist.git
+
+Patch Guideline
+---------------
+
+Patches for PTXdist are always welcome. If you created a patch, send it to
+ptxdist@pengutronix.de for review. Each patch accepted into the master
+repository must be certified to be compatible with PTXdist's license (GPL v2,
+see COPYING). To do this you have to sign your patches (or the ones you apply
+and/or forward). If you can certify the below:
+
+ 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.
+
+then you just add a line saying
+
+ Signed-off-by: Random J Developer <random@developer.example.org>
+
+using your real name (sorry, no pseudonyms or anonymous contributions.) at the
+end of the patch description.
+
+There are some more usual tags (like Acked-by or Reported-by) which only have
+informational character and so are not formally specified here. See the Linux
+kernel (file: Documentation/SubmittingPatches) for how they are used here, too.
--
1.7.10.4
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2013-02-28 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 10:34 Uwe Kleine-König [this message]
2013-02-28 10:58 ` Marc Kleine-Budde
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=1362047677-29294-1-git-send-email-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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