|Deletions are marked like this.||Additions are marked like this.|
|Line 8:||Line 8:|
|a. The package DebPkg:devscripts ships also `querybts`, which dumps the mbox to stdout when started with `querybts --mbox 677375`.||a. The package DebPkg:reportbug ships `querybts`, which dumps the mbox to stdout when started with `querybts --mbox 677375`.|
Using reportbug to follow up on reports has several disadvantages as not CCing other reporters, breaking threading and not allowing inline quoting in any way which is documented in bug report 677375 being marked as wontfix.
Please adhere to the following instructions on how to follow up properly.
- Download the message as a mbox file. There are several ways.
The Web interface showing all the messages of a report adds links to the mbox version of each message. You can either use that to download all messages as an mbox file, for example http://bugs.debian.org/cgi-bin/bugreport.cgi?mbox=yes;bug=677375, or just download the mbox file of the message you want to reply to, for example http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;mbox=yes;bug=677375.
The package devscripts ships the program bts you can use to download the messages with bts show --mbox 677375. This downloads the a mbox file with all messages in it and saves in ~/.devscripts-cache/bts/677375.mbox.
The package reportbug ships querybts, which dumps the mbox to stdout when started with querybts --mbox 677375.
- Import that message into your mail program (MUA) and reply as always making sure to add all relevant people to CC.