hurd/running/debian/patch_submission: Make the pseudo-headers easily copy & pasteable.

1 files changed, 13 insertions, 9 deletions

diff --git a/hurd/running/debian/patch_submission.mdwn b/hurd/running/debian/patch_submission.mdwn
index d2b7b776..1dd8a4db 100644
--- a/hurd/running/debian/patch_submission.mdwn
+++ b/hurd/running/debian/patch_submission.mdwn
@@ -28,20 +28,24 @@ either use the reportbug tool, or just simple mail.  In any case, you should
 follow these guidelines:
 
   * The submission address is <submit@bugs.debian.org>.
+
   * The mail's subject (which will become the bug's title) should be
     `SOURCE-PACKAGE: FTBFS on hurd-i386: REASON`.
-  * The first lines of the mail's body (the so-called *pseudo-header*):
-      * `Severity: important` -- not *serious*.
-      * `Version: VERSION` -- the version of the source package in unstable.
-      * `Tags: patch` -- as/if you include a ready-to-be-applied patch.
-      * `User: debian-hurd@lists.debian.org`
-      * `Usertags: hurd`
 
-Please also add
+  * The first lines of the mail's body (the so-called *pseudo-header*):
 
-`X-Debbugs-CC: debian-hurd@lists.debian.org`
+        Package: PACKAGE
+        Severity: important -- not *serious*
+        Version: VERSION -- the version of the source package in unstable.
+        Tags: patch -- if you include a ready-to-be-applied patch.
+        User: debian-hurd@lists.debian.org
+        Usertags: hurd
+        X-Debbugs-CC: debian-hurd@lists.debian.org
 
-in the mail headers, so that the mailing list knows about your report.
+The last three lines are used to to change the current *User* to the specified
+value (the default is the email sender/from address), specify *Usertags* to add
+the specified tags for the current user, and *X-Debbugs-CC* so that the
+[[mailing list|mailing_lists/debian-hurd]] knows about your report.
 
 In the bug description, mention that the package fails to build on hurd-i386
 and (if possible) quote the failure.  If possible, point to the failing build