2 .\" ---------------------------------------------------------------------------
3 .\" man page for send-pr (by Heinz G. Seidl, hgs@cygnus.com)
4 .\" updated Feb 1993 for GNATS 3.00 by Jeffrey Osier, jeffrey@cygnus.com
6 .\" This file is part of the Problem Report Management System (GNATS)
7 .\" Copyright 1992 Cygnus Support
9 .\" This program is free software; you can redistribute it and/or
10 .\" modify it under the terms of the GNU General Public
11 .\" License as published by the Free Software Foundation; either
12 .\" version 2 of the License, or (at your option) any later version.
14 .\" This program is distributed in the hope that it will be useful,
15 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
16 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
17 .\" General Public License for more details.
19 .\" You should have received a copy of the GNU Library General Public
20 .\" License along with this program; if not, write to the Free
21 .\" Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA
23 .\" ---------------------------------------------------------------------------
25 .TH SEND-PR 1 xVERSIONx "February 1993"
27 send-pr \- send problem report (PR) to a central support site
57 is a tool used to submit
59 .\" SITE ADMINISTRATORS - change this if you use a local default
60 (PRs) to a central support site. In most cases the correct
62 will be the default. This argument indicates the support site which
63 is responsible for the category of problem involved. Some sites may
64 use a local address as a default.
66 values are defined by using the
70 invokes an editor on a problem report template (after trying to fill
71 in some fields with reasonable default values). When you exit the
74 sends the completed form to the
75 .I Problem Report Management System
76 (\fBGNATS\fR) at a central support site. At the support site, the PR
77 is assigned a unique number and is stored in the \fBGNATS\fR database
78 according to its category and submitter-id. \fBGNATS\fR automatically
79 replies with an acknowledgement, citing the category and the PR
82 To ensure that a PR is handled promptly, it should contain your (unique)
83 \fIsubmitter-id\fR and one of the available \fIcategories\fR to identify the
86 to see a list of categories).
87 The PR should also contain a subject header, which is separate to the
89 NetBSD does not use unique \fIsubmitter-id\fR's - all PR's use the
96 .\" template at your site should already be customized with your
97 .\" submitter-id (running `\|\fBinstall-sid\fP \fIsubmitter-id\fP\|' to
98 .\" accomplish this is part of the installation procedures for
100 .\" If this hasn't been done, see your system administrator for your
101 .\" submitter-id, or request one from your support site by invoking
102 .\" .B `send-pr \-\-request\-id'.
103 .\" If your site does not distinguish between different user sites, or if
104 .\" you are not affiliated with the support site, use
108 The more precise your problem description and the more complete your
109 information, the faster your support team can solve your problems.
112 .BI \-f " problem-report"
113 specify a file (\fIproblem-report\fR) which already contains a
114 complete problem report.
116 sends the contents of the file without invoking the editor. If
123 reads from standard input.
125 .BI \-t " mail-address"
126 Change mail address at the support site for problem reports. The
129 is the address used for the default
133 argument rather than this option in nearly all cases.
136 print the form specified by the environment variable
138 on standard output. If
140 is not set, print the standard blank PR template. No mail is sent.
143 print the list of available categories. No mail is sent.
146 sends mail to the default support site, or
148 if specified, with a request for your
165 to submit problem reports rather than mailing them directly. Using
166 both the template and
168 itself will help ensure all necessary information will reach the
173 If the file $GNATS_ROOT/gnats-adm/config exists then it is used
174 to provide newer configuration information. The default value
178 Sets the default for the From and Reply-To fields of the problem report.
179 Defaults to $USER if not set.
182 Sets the default for the Originator field of the problem report.
183 If not set, then the file $HOME/.fullname is used. If
184 $HOME/.fullname is not present, then an attempt is made to query
185 the password file for a full name.
188 The name of a file which contains the default for the Organization field
189 of the problem report.
192 If this is set, then its value is used as the file name of the template for
193 your problem-report editing session. You can use this to start with a
194 partially completed form (for example, a form with the identification
195 fields already completed).
198 Sets the default for the Reply-To field of the problem report. If not
199 set, then it defaults to $LOGNAME.
202 Specifies the temporary directory used for creating the problem report.
203 This directory must exist with write permissions. Defaults to /tmp if
207 Used to set the default site you are reporting bugs to. Defaults to
208 netbsd if not specified.
211 Specifies the editor to invoke on the template. If not set, then the
212 variable EDITOR is used. If neither VISUAL nor EDITOR are
216 .SH "HOW TO FILL OUT A PROBLEM REPORT"
217 Problem reports have to be in a particular form so that a program can
218 easily manage them. Please remember the following guidelines:
222 with each problem report.
224 For follow-up mail, use the same subject line as the one in the automatic
225 acknowledgement. It consists of category, PR number and the original synopsis
226 line. This allows the support site to relate several mail messages to a
227 particular PR and to record them automatically.
229 Please try to be as accurate as possible in the subject and/or synopsis line.
231 The subject and the synopsis line are not confidential. This is
232 because open-bugs lists are compiled from them. Avoid confidential
237 field is to indicate the severity of the problem.
238 The accepted values are:
240 The product, component or concept is completely non-operational or some
241 essential functionality is missing (e.g. kernel panic or program core dumps).
242 No workaround is known.
244 The product, component or concept is not working properly or significant
245 functionality is missing.
246 Problems that would otherwise be considered
250 when a workaround is known.
251 .IP \fBnon-critical\fR
252 The product, component or concept is working in general, but lacks
253 features, has irritating behavior, does something wrong, or doesn't
254 match its documentation.
262 how soon the problem report submitter requires a solution.
263 The accepted values are:
265 A solution is needed as soon as possible.
267 The problem should be solved in the next release.
269 The problem should be solved in a future release.
276 of a problem report can be one of the following:
278 A general software problem (
284 A problem with the manual pages or other documentation.
285 .IP \fBchange-request\fR
286 A request for a change from existing behavior that is not a bug
287 ("It's nice, but it would be better if ...").
289 A support problem or question.
298 or the document \fIReporting Problems With send-pr\fR\ for detailed
299 information on reporting problems
300 .SH "HOW TO SUBMIT TEST CASES, CODE, ETC."
301 Submit small code samples with the PR. Contact the support site for
302 instructions on submitting larger test cases and problematic source
306 copy of PR used in editing session
309 copy of empty PR form, for testing purposes
312 file for rejected PRs
315 Contains the default for the Originator field of the problem
316 report if $NAME is not set
318 .SM $HOME/.organization
319 Contains the default for the Organization field of the problem
320 report if $ORGANIZATION is not set.
323 Contains the default for the Organization field of the problem
324 report if $ORGANIZATION is not set and $HOME/.organization does
326 .SH EMACS USER INTERFACE
327 An Emacs user interface for
329 with completion of field values is part of the
331 distribution (invoked with
337 in the top level directory of the distribution for configuration and
338 installation information. The Emacs LISP template file is
343 An interface to sending PR's is available on the NetBSD website at
344 http://www.NetBSD.org/Gnats/.
345 .SH INSTALLATION AND CONFIGURATION
350 for installation instructions.
352 .I Reporting Problems Using send-pr
353 (also installed as the GNU Info file
357 .\" .BR query-pr (1),
360 .\" .BR queue-pr (8),
365 Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus
368 Copyright (c) 1992, 1993 Free Software Foundation, Inc.
370 Permission is granted to make and distribute verbatim copies of
371 this manual provided the copyright notice and this permission notice
372 are preserved on all copies.
374 Permission is granted to copy and distribute modified versions of this
375 manual under the conditions for verbatim copying, provided that the
376 entire resulting derived work is distributed under the terms of a
377 permission notice identical to this one.
379 Permission is granted to copy and distribute translations of this
380 manual into another language, under the above conditions for modified
381 versions, except that this permission notice may be included in
382 translations approved by the Free Software Foundation instead of in
383 the original English.