Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
cvsbug(8)
Edit
PageHistory
Diff
Info
LikePages
CVSBUG !!!CVSBUG NAME SYNOPSIS DESCRIPTION OPTIONS ENVIRONMENT HOW TO FILL OUT A PROBLEM REPORT HOW TO SUBMIT TEST CASES, CODE, ETC. FILES INSTALLATION AND CONFIGURATION SEE ALSO AUTHORS COPYING ---- !!NAME cvsbug - send problem report (PR) about CVS to a central support site !!SYNOPSIS __cvsbug__ [[ ''site'' ] [[ __-f__ ''problem-report'' ] [[ __-t__ ''mail-address'' ] [[ __-P__ ] [[ __-L__ ] [[ __--request-id__ ] [[ __-v__ ] !!DESCRIPTION __cvsbug__ is a tool used to submit ''problem reports'' (PRs) to a central support site. In most cases the correct ''site'' will be the default. This argument indicates the support site which is responsible for the category of problem involved. Some sites may use a local address as a default. ''site'' values are defined by using the aliases(5). __cvsbug__ invokes an editor on a problem report template (after trying to fill in some fields with reasonable default values). When you exit the editor, __cvsbug__ sends the completed form to the ''Problem Report Management System'' (__GNATS__) at a central support site. At the support site, the PR is assigned a unique number and is stored in the __GNATS__ database according to its category and submitter-id. __GNATS__ automatically replies with an acknowledgement, citing the category and the PR number. To ensure that a PR is handled promptly, it should contain your (unique) ''submitter-id'' and one of the available ''categories'' to identify the problem area. (Use __`cvsbug -L'__ to see a list of categories.) The __cvsbug__ template at your site should already be customized with your submitter-id (running `__install-sid__ ''submitter-id''' to accomplish this is part of the installation procedures for __cvsbug__). If this hasn't been done, see your system administrator for your submitter-id, or request one from your support site by invoking __`cvsbug --request-id'.__ If your site does not distinguish between different user sites, or if you are not affiliated with the support site, use __`net'__ for this field. The more precise your problem description and the more complete your information, the faster your support team can solve your problems. !!OPTIONS __-f__ ''problem-report'' specify a file (''problem-report'') which already contains a complete problem report. __cvsbug__ sends the contents of the file without invoking the editor. If the value for ''problem-report'' is __`-'__, then __cvsbug__ reads from standard input. __-t__ ''mail-address'' Change mail address at the support site for problem reports. The default ''mail-address'' is the address used for the default ''site''. Use the ''site'' argument rather than this option in nearly all cases. __-P__ print the form specified by the environment variable __PR_FORM__ on standard output. If __PR_FORM__ is not set, print the standard blank PR template. No mail is sent. __-L__ print the list of available categories. No mail is sent. __--request-id__ sends mail to the default support site, or ''site'' if specified, with a request for your ''submitter-id''. If you are not affiliated with ''site'', use a ''submitter-id'' of __net__'. __-v__ Display the __cvsbug__ version number. Note: use __cvsbug__ to submit problem reports rather than mailing them directly. Using both the template and __cvsbug__ itself will help ensure all necessary information will reach the support site. !!ENVIRONMENT The environment variable __EDITOR__ specifies the editor to invoke on the template. default: __vi__ If the environment variable __PR_FORM__ is set, then its value is used as the file name of the template for your problem-report editing session. You can use this to start with a partially completed form (for example, a form with the identification fields already completed). !!HOW TO FILL OUT A PROBLEM REPORT Problem reports have to be in a particular form so that a program can easily manage them. Please remember the following guidelines: describe only __one problem__ with each problem report. For follow-up mail, use the same subject line as the one in the automatic acknowledgent. It consists of category, PR number and the original synopsis line. This allows the support site to relate several mail messages to a particular PR and to record them automatically. Please try to be as accurate as possible in the subject and/or synopsis line. The subject and the synopsis line are not confidential. This is because open-bugs lists are compiled from them. Avoid confidential information there. See the GNU __Info__ file __cvsbug.info__ or the document ''Reporting Problems With cvsbug'' for detailed information on reporting problems !!HOW TO SUBMIT TEST CASES, CODE, ETC. Submit small code samples with the PR. Contact the support site for instructions on submitting larger test cases and problematic source code. !!FILES /tmp/p$$ copy of PR used in editing session /tmp/pf$$ copy of empty PR form, for testing purposes /tmp/pbad$$ file for rejected PRs !!INSTALLATION AND CONFIGURATION See __INSTALL__ for installation instructions. !!SEE ALSO __gnats__(l), query-pr(1), __edit-pr__(1), gnats(8), queue-pr(8), __at-pr__(8), mkcat(8), mkdist(8). !!AUTHORS Jeffrey Osier, Brendan Kehoe, Jason Merrill, Heinz G. Seidl (Cygnus Support) !!COPYING Copyright (c) 1992, 1993 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. ----
One page links to
cvsbug(8)
:
Man8c
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
