summaryrefslogtreecommitdiff
path: root/includes/squeeze/common/doc/bug-log-mailserver.txt
diff options
context:
space:
mode:
Diffstat (limited to 'includes/squeeze/common/doc/bug-log-mailserver.txt')
-rw-r--r--includes/squeeze/common/doc/bug-log-mailserver.txt59
1 files changed, 31 insertions, 28 deletions
diff --git a/includes/squeeze/common/doc/bug-log-mailserver.txt b/includes/squeeze/common/doc/bug-log-mailserver.txt
index 764d25a9e..447a059f7 100644
--- a/includes/squeeze/common/doc/bug-log-mailserver.txt
+++ b/includes/squeeze/common/doc/bug-log-mailserver.txt
@@ -1,30 +1,32 @@
+Introduction to the bug system request server
+
There is a mailserver which can send the bug reports and indices as
plain text on request.
To use it you send a mail message to request@bugs.debian.org. The
- Subject of the message is ignored, except for generating the Subject of
- the reply.
+ Subject of the message is ignored, except for generating the Subject
+ of the reply.
The body you send should be a series of commands, one per line. You'll
receive a reply which looks like a transcript of your message being
- interpreted, with a response to each command. No notifications are sent
- to anyone for the commands listed here and the mail isn't logged
+ interpreted, with a response to each command. No notifications are
+ sent to anyone for the commands listed here and the mail isn't logged
anywhere publicly available.
Any text on a line starting with a hash sign # is ignored; the server
will stop processing when it finds a line with a control terminator (
- quit, thank you, or two hyphens are common examples). It will also stop
- if it encounters too many unrecognised or badly-formatted commands. If
- no commands are successfully handled it will send the help text for the
- server.
+ quit, thank you, or two hyphens are common examples). It will also
+ stop if it encounters too many unrecognised or badly-formatted
+ commands. If no commands are successfully handled it will send the
+ help text for the server.
Commands available
send bugnumber
send-detail bugnumber
Requests the transcript for the bug report in question.
- send-detail sends all of the "boring" messages in the transcript
- as well, such as the various auto-acks.
+ send-detail sends all of the "boring" messages in the
+ transcript as well, such as the various auto-acks.
index [full]
index-summary by-package
@@ -34,8 +36,8 @@ Commands available
number, respectively.
index-maint
- Requests the index page giving the list of maintainers with bugs
- (open and recently-closed) in the tracking system.
+ Requests the index page giving the list of maintainers with
+ bugs (open and recently-closed) in the tracking system.
index maint maintainer
Requests the index pages of bugs in the system for the
@@ -55,8 +57,8 @@ Commands available
send-unmatched last|-1
send-unmatched old|-2
Requests logs of messages not matched to a particular bug
- report, for this week, last week and the week before. (Each week
- ends on a Wednesday.)
+ report, for this week, last week and the week before. (Each
+ week ends on a Wednesday.)
getinfo filename
Request a file containing information about package(s) and or
@@ -100,18 +102,19 @@ Commands available
--
Stops processing at this point of the message. After this you
may include any text you like, and it will be ignored. You can
- use this to include longer comments than are suitable for #, for
- example for the benefit of human readers of your message
- (reading it via the tracking system logs or due to a CC or BCC).
+ use this to include longer comments than are suitable for #,
+ for example for the benefit of human readers of your message
+ (reading it via the tracking system logs or due to a CC or
+ BCC).
#...
One-line comment. The # must be at the start of the line.
debug level
- Sets the debugging level to level, which should be a nonnegative
- integer. 0 is no debugging; 1 is usually sufficient. The
- debugging output appears in the transcript. It is not likely to
- be useful to general users of the bug system.
+ Sets the debugging level to level, which should be a
+ nonnegative integer. 0 is no debugging; 1 is usually
+ sufficient. The debugging output appears in the transcript. It
+ is not likely to be useful to general users of the bug system.
There is a reference card for the mailservers, available via the WWW,
in bug-mailserver-refcard.txt or by email using the refcard command
@@ -119,19 +122,19 @@ Commands available
If you wish to manipulate bug reports you should use the
control@bugs.debian.org address, which understands a superset of the
- commands listed above. This is described in another document, available
- on the WWW, in the file bug-maint-mailcontrol.txt, or by sending help
- to control@bugs.
+ commands listed above. This is described in another document,
+ available on the WWW, in the file bug-maint-mailcontrol.txt, or by
+ sending help to control@bugs.
- In case you are reading this as a plain text file or via email: an HTML
- version is available via the bug system main contents page
+ In case you are reading this as a plain text file or via email: an
+ HTML version is available via the bug system main contents page
http://www.debian.org/Bugs/.
- __________________________________________________________________
+ _________________________________________________________________
Debian BTS administrators <owner@bugs.debian.org>
Debian bug tracking system
Copyright © 1999 Darren O. Benham, 1997, 2003 nCipher Corporation Ltd,
1994-1997 Ian Jackson.
- __________________________________________________________________
+ _________________________________________________________________