| | 1 | On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko suggests: |
| | 2 | |
| | 3 | I really like using the mailing list for patches, because the mailing |
| | 4 | list is a public, on-the-record conversation that includes everyone. |
| | 5 | |
| | 6 | What about this: |
| | 7 | |
| | 8 | darcs send -o patch.darcspatch |
| | 9 | darcs diff -u -p"${PATCHRE}" > patch.diff.txt |
| | 10 | |
| | 11 | and then send both to the mailing list as attachments? This is more |
| | 12 | work for the submitter, as they have to attach the files to a message |
| | 13 | and send the message (instead of allowing "darcs send" to send the |
| | 14 | message for them). |
| | 15 | |
| | 16 | The good things about this are (a) hopefully everyone can see the |
| | 17 | patch contents in-line in the mail and (b) you can add a "cover |
| | 18 | letter" -- a message to the mailing list about the patch. |
