This is a database of sites which submit bugs to your support site. It contains six fields delineated by colons. Lines beginning with # will be ignored.
Entries are of the format:
submitter-idlisted in the file will be the default for PRs that arrive with invalid or empty submitter fields.
notify-about-expired-prsentry set to true (see Overall database configuration, gnats will use this field to schedule when it should notify the gnats-admin, responsible person and submitter contact that the PR wasn't analyzed within the agreed response time. Business hours and business-week days are set in the dbconfig file. For information on
at-pr, the program which sends out this reminder, see Timely Reminders.
responsiblefile). Incoming bugs from submitter are sent to this contact. Optionally, this field can be left blank.
A few example entries in the submitters file:
univ-hell:University of Hades:eternal:3:beelzebub:lucifer tta:Telephones and Telegraphs of America:support:720:dave:
In this example, when a PR comes in from the University of Hades (who
has an eternal contract), it should have univ-hell in its
Submitter-Id field. This Problem Report goes to
(who should be in the responsible file), and if it is not
analyzed within three business hours a reminder message is sent.
lucifer also receives a copy of the bug, and a copy of the
reminder message as well (if it is sent). When Telephones and
Telegraphs of America utilizes their support contract and submits a bug,
a copy is sent only to
dave, who has 720 business hours to return
an analysis before a reminder is sent.
To disable the feature of gnats which tracks the
Submitter-Id, simply alter the submitters file to only
contain one submitter-id value, and instruct your submitters to
ignore the field.