NetarchiveSuite|
⇤ ← Revision 1 as of 2009-11-17 08:16:54
Size: 705
Comment: Generated the documentation branch for 3.12
|
← Revision 2 as of 2010-08-16 10:24:57 ⇥
Size: 709
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Anchor(Sending Patches)]] | <<Anchor(Sending Patches)>> |
| Line 3: | Line 3: |
| [[Action(edit)]] | <<Action(edit)>> |
| Line 7: | Line 7: |
| If possible, use our [https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse patch-tracker] to transmit the patch to us. The [:Process/Create_Tracker_Issue: Create Tracker Issue process] describes how. | If possible, use our [[https://gforge.statsbiblioteket.dk/tracker/?atid=107&group_id=7&func=browse|patch-tracker]] to transmit the patch to us. The [[Process/Create Tracker Issue| Create Tracker Issue process]] describes how. |
| Line 9: | Line 9: |
| If sending patches by email, please follow the [:Process/Create_Tracker_Issue: Create Tracker Issue process] as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting. | If sending patches by email, please follow the [[Process/Create Tracker Issue| Create Tracker Issue process]] as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting. |
Sending Patches
We're always happy to receive patches, though we may choose not to apply them if the implemented features go against our purposes or the code quality is too low.
If possible, use our patch-tracker to transmit the patch to us. The Create Tracker Issue process describes how.
If sending patches by email, please follow the Create Tracker Issue process as far as possible, and please send files as attachments rather than inline, as mail readers tend to mess up important formatting.