Don, On Wednesday, September 25, 2024 9:56:15 PM MST Don Armstrong wrote: > On Mon, 23 Sep 2024, Soren Stoutner wrote: > > However, that page is entitled, "How to report a bug in Debian using > > reportbug". It would be valuable to document it on > > https://www.debian.org/ Bugs/server-control entitled "Introduction to > > the bug control and manipulation mailserver" as users are unlikely to > > be searching for information about how to manipulate an existing bug > > on a page with instructions on how to report a new bug. > > The bug control mailserver is cont...@bugs.debian.org, for which -1 > doesn't apply unless you've used `clone`. > > The initial population of -1 only applies to the Control: pseudoheader, > and that pseudoheader is documented here: > https://www.debian.org/Bugs/Reporting#control > > It seems reasonable to > https://www.debian.org/Bugs/Developer#followup to > https://www.debian.org/Bugs/Reporting#control (and the other > pseudoheaders that are valid for follow up messages), but that > documentation doesn't belong in the server-control documentation.
I see your point that this information fits well in: https://www.debian.org/bugs/Developer#followup https://www.debian.org/bugs/Reporting#control However, https://www.debian.org/bugs/server-control currently contains the following text: "In case you need to write a message to the bug and also manipulate the bug's metadata, the commands can also be included in the mail to n...@bugs.debian.org. Do this by starting the mail with the commands prefixed by Control: .” Seeing as how this mentions using n...@bugs.debian.org and starting the email with commands prefixed by Control:, it seems appropriate that this should also mention that the bug number in n...@bugs.debian.org can be referenced using -1. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
