From 2d72fa994b0054d6972858e60de95393ff12ebe5 Mon Sep 17 00:00:00 2001
From: nejucomo <>
Date: Mon, 5 Nov 2007 07:40:02 +0000
Subject: [PATCH] [Imported from Trac: page Patches, version 1]

---
 Patches.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 Patches.md

diff --git a/Patches.md b/Patches.md
new file mode 100644
index 0000000..a79cc70
--- /dev/null
+++ b/Patches.md
@@ -0,0 +1,18 @@
+On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko suggests:
+
+> I really like using the mailing list for patches, because the mailing
+> list is a public, on-the-record conversation that includes everyone.
+
+> What about this:
+
+> darcs send -o patch.darcspatch
+> darcs diff -u -p"${PATCHRE}" > patch.diff.txt
+
+> and then send both to the mailing list as attachments?  This is more
+> work for the submitter, as they have to attach the files to a message
+> and send the message (instead of allowing "darcs send" to send the
+> message for them).
+
+> The good things about this are (a) hopefully everyone can see the
+> patch contents in-line in the mail and (b) you can add a "cover
+> letter" -- a message to the mailing list about the patch.
\ No newline at end of file