Mercurial > hg > octave-jordi
comparison SENDING-PATCHES @ 2330:12ff450cbb1f
[project @ 1996-07-19 01:39:22 by jwe]
Initial revision
| author | jwe |
|---|---|
| date | Fri, 19 Jul 1996 01:49:31 +0000 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 2329:30c606bec7a8 | 2330:12ff450cbb1f |
|---|---|
| 1 [This was originally from Richard Stallman who was writing about | |
| 2 Emacs. --jwe] | |
| 3 | |
| 4 A reminder for those sending patches for Octave: | |
| 5 | |
| 6 * Always make the diffs with context. Preferably use diff -c. It | |
| 7 is unreliable to install a diff without context, and therefore we | |
| 8 probably will not take the risk of trying; instead we will | |
| 9 probably ask you to send a context diff. You might as well send | |
| 10 that in your first message. | |
| 11 | |
| 12 * Always send change log entries with your patches. Itemize the | |
| 13 entries so that they list each of the functions and variables | |
| 14 changed. Look at the ChangeLog files and follow our conventions | |
| 15 regarding what information to include and what style to use. | |
| 16 | |
| 17 * If the patch is to fix a bug, send a detailed bug report for the | |
| 18 bug. Make this just as detailed as if you did not have any fix | |
| 19 for it. This information is vital for convincing the maintainer | |
| 20 that your fix is necessary and should be installed. Also, if your | |
| 21 fix would cause some other sort of problem, the bug report may | |
| 22 enable the maintainer to find some other correct fix. | |
| 23 | |
| 24 Everyone, please read the Bugs chapter in the Octave manual to see | |
| 25 other guidelines on how to write a bug report that makes it possible | |
| 26 to fix a bug. |