-
Notifications
You must be signed in to change notification settings - Fork 130
Code SVN Patches Additions
Proposed changes to code should probably be presented to the original/maintaining author as a courtesy. They may already have your change in the works so you don't duplicate the effort, also there may be reasons behind not changing it. So contact them directly, or through the main mailing list to discuss the changes. This should help in creating an improved patch/change and avoid unintended problems.
Generally speaking any submissions should be in an email attachment. This way the content will remain intact and exactly as it needs to be (especially diffs). Often email programs, mailing lists and transport mailers will add unwanted characters and line breaks, using an attachment should keep what you submitted as-is, and usable especially for patches.
#patchesPatches:
Patches may be submitted directly to the mailing list. We prefer the patch to be an attachment, as it is easier and more accurate to apply a patch when it is a standalone text file.( unified diff's are essential to resolves assumptions about having identical reference code)
If it is a minor change, you should include the location of the code file (eg ./mh/web/bin/file.pl). The line number that the change is on (if available) Please supply at least one preceding line of code that is not being changes, The line(s) that you want to add/delete/change, and the next line in the file that is unchanged. This way we will have a reference in the code file to identify the location of the change
#CodeCode (submission)
Code modules can be submitted (as an attachment) directly to the mailing list. Please provide a description of what this code accomplishes, and any recommended location in the mh code tree. It is a good idea to create an archive file (zip tar, tgz ...) in order to preserve all the contents, and avoid code from being interpreted as 'unsafe' by many mail services