X-Git-Url: http://git.silcnet.org/gitweb/?a=blobdiff_plain;f=public_html%2Fhtml%2Fcontribute.php;h=d6992df05daed8c297b21fdc31b26c6b9e8cb805;hb=e7b6c157b80152bf9fb9266e6bdd93f9fb0db776;hp=d05558ac9cdb2ece7d88e4251097ece7e7ec30de;hpb=293fd052c6c228fae09f1e779dc5f79b37dec8ce;p=silc.git
diff --git a/public_html/html/contribute.php b/public_html/html/contribute.php
index d05558ac..d6992df0 100644
--- a/public_html/html/contribute.php
+++ b/public_html/html/contribute.php
@@ -20,6 +20,47 @@ described in that document.
There is anonymous CVS acccess for those who want to participate the
development process. See the CVS page.
+
+Submitting Patches to Mailing List
+
+Please follow these instructions when you are submitting a patch to the
+silc-devel mailing list.
+
+
+
- | +Use the unified output format for the diff (diff -u) + |
- | +Use diff, not cvs diff + |
- | +Send the patch to the mailing list, and add those people that should know +about it on CC: + |
- | +Submit ready patches. If they are not ready then sending them to +people who are involved in the development is preferred. The patch might +face several round trips so sending patches which are ready is preffered + |
- | +Include the patch in the body of the email or attach it + |
- | +Send separate patches for every bugfix or feature + |
- | +If you think that your work is benefical to the development of the +SILC and would like to be listed in the CREDITS file in SILC packages, you +can submit patches for the CREDITS file too. Nobody will be added there +without a patch, this way those who don't want to see their name there +won't get there + |
- | +Do not submit bugs ;) + |