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

---
 Patches.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/Patches.md b/Patches.md
index a79cc70..5ad8b19 100644
--- a/Patches.md
+++ b/Patches.md
@@ -5,14 +5,16 @@ On the [/cgi-bin/mailman/listinfo/tahoe-dev tahoe-dev mailing list], Zooko sugge
 
 > What about this:
 
-> darcs send -o patch.darcspatch
-> darcs diff -u -p"${PATCHRE}" > patch.diff.txt
+```
+  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
+> The good things about this are:
+  * hopefully everyone can see the patch contents in-line in the mail, and
+  * you can add a "cover letter" -- a message to the mailing list about the patch.
\ No newline at end of file