Index: HACKING
===================================================================
--- HACKING	(revision 15344)
+++ HACKING	(working copy)
@@ -1140,13 +1140,20 @@
 instead.
 
 The email message should start off with a log message, as described in
-"Writing log messages" above.  The patch itself should be in unified
-diff format (e.g., with "svn diff").  Send the patch as an attachment,
-with a mime-type of text/x-diff, text/x-patch, or text/plain.  (Most
-people's mailreaders can display those inline, and having the patch as
-an attachment allows them to extract the patch from the message
-conveniently.)  
+"Writing log messages" above. It should be enclosed in triple square
+brackets just like this:
 
+   [[[
+   * HACKING
+     Improving the patch submission guidelines
+   ]]]
+
+The patch itself should be in unified diff format (e.g., with "svn
+diff").  Send the patch as an attachment, with a mime-type of
+text/x-diff, text/x-patch, or text/plain.  (Most people's mailreaders
+can display those inline, and having the patch as an attachment allows
+them to extract the patch from the message conveniently.)
+
 If you can't attach the patch with one of these mime-types, or if the
 patch is very short, then just include it directly in the body of your
 message.  But if your mailer forces wrapping of long lines, then you