summaryrefslogtreecommitdiffstats
path: root/README.devel
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2013-02-28 11:34:37 +0100
committerMarc Kleine-Budde <mkl@pengutronix.de>2013-02-28 11:57:56 +0100
commit5b2b0454e214514386b42812e7738356ae0db9d2 (patch)
tree3411a053e6125549f38137e52acefb3ab70a16d0 /README.devel
parent4dd9a5f35050290de3b5ba9e668c0f6e0aa9eb93 (diff)
downloadptxdist-5b2b0454e214514386b42812e7738356ae0db9d2.tar.gz
ptxdist-5b2b0454e214514386b42812e7738356ae0db9d2.tar.xz
Formalize the meaning of Signed-off-by
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> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'README.devel')
-rw-r--r--README.devel55
1 files changed, 55 insertions, 0 deletions
diff --git a/README.devel b/README.devel
new file mode 100644
index 000000000..028fb7349
--- /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.