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 .\" $FreeBSD: src/gnu/usr.bin/send-pr/send-pr.1,v 1.9.2.6 2003/05/03 22:02:49 keramida Exp $
26 .\" $DragonFly: src/gnu/usr.bin/send-pr/Attic/send-pr.1,v 1.2 2003/06/17 04:25:48 dillon Exp $
28 .TH SEND-PR 1 3.113 "February 1993"
30 send-pr \- send problem report (PR) to a central support site
73 is a tool used to submit
75 .\" SITE ADMINISTRATORS - change this if you use a local default
76 (PRs) to a central support site. In most cases the correct
78 will be the default. This argument indicates the support site which
79 is responsible for the category of problem involved. Some sites may
80 use a local address as a default.
82 values are defined by using the
86 invokes an editor on a problem report template (after trying to fill
87 in some fields with reasonable default values). When you exit the
90 sends the completed form to the
91 .I Problem Report Management System
92 (\fBGNATS\fR) at a central support site. At the support site, the PR
93 is assigned a unique number and is stored in the \fBGNATS\fR database
94 according to its category and submitter-id. \fBGNATS\fR automatically
95 replies with an acknowledgement, citing the category and the PR
98 To ensure that a PR is handled promptly, it should contain
99 one of the available \fIcategories\fR to identify the
102 to see a list of categories.)
104 The more precise your problem description and the more complete your
105 information, the faster your support team can solve your problems.
108 .BI \-f " problem-report"
109 specify a file (\fIproblem-report\fR) which already contains a
110 complete problem report.
112 sends the contents of the file without invoking the editor. If
119 reads from standard input.
122 Give the problem report the severity
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.
140 header of the message.
148 Binary files are uuencoded.
151 print the form specified by the environment variable
153 on standard output. If
155 is not set, print the standard blank PR template. No mail is sent.
158 print the list of available categories. No mail is sent.
164 This may also be specified as
169 to submit problem reports rather than mailing them directly. Using
170 both the template and
172 itself will help ensure all necessary information will reach the
174 .SH FREEBSD CATEGORIES
177 This used to be for the advocacy WWW pages. Not quite sure what is used
181 Alpha processor specific problems.
184 Corrections or enhancements to system executables.
187 Corrections or enhancements to the system configuration files.
190 Corrections or enhancements to the manpages or other documentation.
193 Corrections or enhancements to the GNU contributed software.
196 Intel x86 processor specific problems.
199 Intel ia64 processor specific problems.
202 Problems related to Java.
205 Changes or enhancements to the architecture independent kernel sources.
208 Problems that don't fit into any of the other categories.
211 Corrections or enhancements (including new ports) to the ports collection.
214 PowerPC processor specific problems.
217 SPARC processor specific problems.
220 Standards conformance issues.
223 Changes or enhancements to the FreeBSD website.
225 The environment variable
227 specifies the editor to invoke on the template.
232 If the environment variable
234 is set, its value is used as the path + command line arguments of the
235 executable to be invoked for sending the problem report (which will be
236 provided via standard input).
238 This can be useful if you either use a MTA other than sendmail or need
239 to provide additional parameters, such as the envelope sender on
240 machines without a valid FQDN.
243 .B /usr/sbin/sendmail -oi -t
245 If the environment variable
247 is set, then its value is used as the file name of the template for
248 your problem-report editing session. You can use this to start with a
249 partially completed form (for example, a form with the identification
250 fields already completed).
251 .SH "HOW TO FILL OUT A PROBLEM REPORT"
252 Problem reports have to be in a particular form so that a program can
253 easily manage them. Please remember the following guidelines:
257 with each problem report.
259 For follow-up mail, use the same subject line as the one in the automatic
260 acknowledgement. It consists of category, PR number and the original synopsis
261 line. This allows the support site to relate several mail messages to a
262 particular PR and to record them automatically.
264 Please try to be as accurate as possible in the subject and/or synopsis line.
266 The subject and the synopsis line are not confidential. This is
267 because open-bugs lists are compiled from them. Avoid confidential
274 or the document \fIReporting Problems With send-pr\fR\ for detailed
275 information on reporting problems
276 .SH "HOW TO SUBMIT TEST CASES, CODE, ETC."
277 Submit small code samples with the PR. Contact the support site for
278 instructions on submitting larger test cases and problematic source
281 .ta \w'/tmp/pbad$$ 'u
282 /tmp/p$$ copy of PR used in editing session
284 /tmp/pf$$ copy of empty PR form, for testing purposes
286 /tmp/pbad$$ file for rejected PRs
287 .SH EMACS USER INTERFACE
288 An Emacs user interface for
290 with completion of field values is part of the
292 distribution (invoked with
298 in the top level directory of the distribution for configuration and
299 installation information. The Emacs LISP template file is
303 .SH INSTALLATION AND CONFIGURATION
308 for installation instructions.
310 .I Reporting Problems Using send-pr
311 (also installed as the GNU Info file
314 Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus
317 Copyright (c) 1992, 1993 Free Software Foundation, Inc.
319 Permission is granted to make and distribute verbatim copies of
320 this manual provided the copyright notice and this permission notice
321 are preserved on all copies.
323 Permission is granted to copy and distribute modified versions of this
324 manual under the conditions for verbatim copying, provided that the
325 entire resulting derived work is distributed under the terms of a
326 permission notice identical to this one.
328 Permission is granted to copy and distribute translations of this
329 manual into another language, under the above conditions for modified
330 versions, except that this permission notice may be included in
331 translations approved by the Free Software Foundation instead of in
332 the original English.