send-pr.texi revision 67908
1193326Sed@c $FreeBSD: head/gnu/usr.bin/send-pr/doc/send-pr.texi 67908 2000-10-29 22:05:52Z steve $ 2193326Sed 3193326Sed\input texinfo @c -*-texinfo-*- 4193326Sed@setfilename send-pr.info 5193326Sed@settitle Reporting Problems Using send-pr 6193326Sed 7193326Sed@setchapternewpage odd 8193326Sed 9193326Sed@include version.texi 10193326Sed@set SENDPR 11193326Sed 12193326Sed@ifinfo 13193326Sed@format 14193326SedSTART-INFO-DIR-ENTRY 15193326Sed* send-pr: (send-pr). Reporting problems--using send-pr 16200583SrdivackyEND-INFO-DIR-ENTRY 17251662Sdim@end format 18249423Sdim@end ifinfo 19249423Sdim 20249423Sdim@ifinfo 21251662SdimCopyright @copyright{} 1993, 1994, 1995 Free Software Foundation, Inc. 22212904Sdim 23212904SdimPermission is granted to make and distribute verbatim copies of 24212904Sdimthis manual provided the copyright notice and this permission notice 25243830Sdimare preserved on all copies. 26251662Sdim 27251662Sdim@ignore 28251662SdimPermission is granted to process this file through TeX and print the 29251662Sdimresults, provided the printed document carries a copying permission 30251662Sdimnotice identical to this one except for the removal of this paragraph 31251662Sdim(this paragraph not being relevant to the printed manual). 32251662Sdim 33251662Sdim@end ignore 34251662Sdim 35251662SdimPermission is granted to copy and distribute modified versions of this 36251662Sdimmanual under the conditions for verbatim copying, provided also that 37239462Sdimthe entire resulting derived work is distributed under the terms of a 38193326Sedpermission notice identical to this one. 39193326Sed 40193326SedPermission is granted to copy and distribute translations of this manual 41193326Sedinto another language, under the above conditions for modified versions. 42193326Sed@end ifinfo 43193326Sed 44263508Sdim@titlepage 45263508Sdim@finalout 46263508Sdim@title Reporting Problems 47263508Sdim@subtitle Using @code{send-pr}, version @value{VERSION} 48263508Sdim@subtitle October 1993 49263508Sdim@author Jeffrey M. Osier 50263508Sdim@author Cygnus Support 51263508Sdim@page 52263508Sdim 53263508Sdim@vskip 0pt plus 1filll 54263508Sdim 55263508SdimCopyright @copyright{} 1993, 1994, 1995 Free Software Foundation, Inc. 56263508Sdim 57263508SdimPermission is granted to make and distribute verbatim copies of 58263508Sdimthis manual provided the copyright notice and this permission notice 59193326Sedare preserved on all copies. 60193326Sed 61193326SedPermission is granted to copy and distribute modified versions of this 62193326Sedmanual under the conditions for verbatim copying, provided also that 63193326Sedthe entire resulting derived work is distributed under the terms of a 64193326Sedpermission notice identical to this one. 65193326Sed 66193326SedPermission is granted to copy and distribute translations of this manual 67193326Sedinto another language, under the above conditions for modified versions. 68193326Sed 69193326Sed@end titlepage 70193326Sed 71193326Sed@c --------------------------------------------------------------- 72193326Sed@node Top 73221345Sdim@top Overview 74193326Sed@cindex foreword to @code{send-pr} 75193326Sed@cindex overview to @code{send-pr} 76193326Sed@cindex introduction to @code{send-pr} 77193326Sed 78193326SedThis manual documents @code{send-pr}, 79193326Sed@ifinfo 80193326Sedversion @value{VERSION}, 81193326Sed@end ifinfo 82193326Sedwhich uses electronic mail to submit support questions and problem 83193326Sedreports to a central Support Site. No body of work is perfect, and 84193326Sedsupport organizations understand this; @code{send-pr} is designed to 85193326Sedallow users who have problems to submit reports of these problems to 86193326Sedsites responsible for supporting the products in question, in a defined 87193326Sedform which can be read by an electronically managed database. 88193326Sed 89193326Sed@cindex GNATS 90193326Sed@code{send-pr} is part of a suite of programs known collectively as 91193326Sed@sc{gnats}, the @sc{gnu} Problem Report Management System. @sc{gnats} 92193326Sedconsists of several programs which, used in concert, formulate and 93193326Sedpartially administer a database of @dfn{Problem Reports}, or @dfn{PRs}, 94193326Sedat a central Support Site. A PR goes through several states in its 95193326Sedlifetime; @sc{gnats} tracks the PR and all information associated with it 96193326Sedthrough each state and finally acts as an archive for PRs which have 97193326Sedbeen @dfn{closed}. 98193326Sed 99193326SedBecause @code{send-pr} exists as a shell (@file{/bin/sh}) script and as 100193326Sedan Elisp file for use with @sc{gnu} Emacs, it can be used from any 101193326Sedmachine on your network which can run a shell script and/or Emacs. 102193326Sed 103193326SedIn general, you can use any editor and mailer to submit valid Problem 104193326SedReports, as long as the format required by @sc{gnats} is preserved. 105193326Sed@code{send-pr} automates the process, however, and ensures that certain 106198092Srdivackyfields necessary for automatic processing are present. @code{send-pr} 107198092Srdivackyis strongly recommended for all initial problem-oriented correspondence 108212904Sdimwith your Support Site. The organization you submit Problem Reports to 109234353Sdimsupplies an address to which further information can be sent; the person 110234353Sdimresponsible for the category of the problem you report contacts you 111226633Sdimdirectly. 112210299Sed 113193326Sed@menu 114234982Sdim* send-pr in detail:: Details about send-pr and GNATS 115249423Sdim* Invoking send-pr:: Editing and sending PRs 116199990Srdivacky* An Example:: A working example 117234982Sdim* Installing send-pr:: Installing send-pr on your system 118234982Sdim* Index:: 119234982Sdim@end menu 120234982Sdim 121234982Sdim@node send-pr in detail 122234982Sdim@chapter Details about send-pr and GNATS 123234982Sdim 124234982Sdim@cindex details about @code{send-pr} 125234982Sdim@cindex Problem Reports 126234982SdimA @dfn{Problem Report} is a message that describes a problem you are 127234982Sdimhaving with a body of work. @code{send-pr} organizes this message into 128234982Sdima form which can be understood and automatically processed by @sc{gnats}, 129263508Sdimthe @sc{gnu} Problem Report Management System. A Problem Report is 130263508Sdimorganized into @dfn{fields} which contain data describing you, your 131263508Sdimorganization, and the problem you are announcing (@pxref{Fields,,Problem 132263508SdimReport format}). Problem Reports go through several defined states in 133263508Sdimtheir lifetimes, from @dfn{open} to @dfn{closed} (@pxref{States,,States 134263508Sdimof Problem Reports}). 135263508Sdim 136263508Sdim@menu 137263508Sdim* States:: States of Problem Reports 138263508Sdim* Fields:: Problem Report format 139263508Sdim@end menu 140263508Sdim 141263508Sdim@include states.texi 142263508Sdim 143263508Sdim@include fields.texi 144263508Sdim 145263508Sdim@node Invoking send-pr 146263508Sdim@chapter Editing and sending PRs 147263508Sdim@cindex editing and sending PRs 148263508Sdim@cindex sending PRs 149263508Sdim@cindex invoking send-pr 150263508Sdim@cindex using send-pr 151263508Sdim@cindex generating new PRs 152263508Sdim 153263508Sdim@include s-usage.texi 154263508Sdim 155263508Sdim@node An Example 156263508Sdim@chapter An Example 157263508Sdim@cindex an example 158263508Sdim@cindex example PR 159263508Sdim@cindex Cygnus Solutions 160263508Sdim@cindex @sc{gnu} software support 161234982SdimCygnus Solutions in Sunnyvale, CA, uses @sc{gnats} and @code{send-pr} 162234982Sdimextensively for their support activities. As a support company, Cygnus 163234982Sdimfinds problem tracking to be a crucial part of everyday business. 164234982SdimCygnus supports the @sc{gnu} compiling tools (including @sc{gnats} and 165234982Sdim@code{send-pr}) over several many platforms 166234982Sdim 167234982SdimWith each shipment of the Cygnus Solutions Developer's Kit, customers 168193326Sedreceive the latest version of @code{send-pr}, which contains an 169193326Sedup-to-date listing of valid categories (values for the @code{>Category:} 170193326Sedfield). Using these tools, Cygnus' customers can communicate their 171221345Sdimproblems to Cygnus effectively and receive automatic confirmation of 172193326Sedreceipt as well as notification of changes in the status of their 173193326Sedreported problems. Much of Cygnus' support mechanism relies on 174193326Sedelectronic mail. 175193326Sed 176193326SedAs an example, let's pretend we're a customer of Cygnus Solutions, and 177234982Sdimthat we're having a problem compiling some of our software using the 178193326Sed@sc{gnu} C compiler, which Cygnus supports. 179193326Sed 180193326SedAssume that we're getting an error in our @code{bifrabulator} program 181193326Sedwherein the @samp{prestidigitation} routines don't match with the 182198092Srdivacky@samp{whatsitsname}. We've made sure we're following the rules of the 183212904Sdimprogram and checked the Release Notes from Cygnus and found that the bug 184226633Sdimisn't already known. In other words, we're pretty sure we've found a 185226633Sdimbug. 186226633Sdim 187221345Sdim@cindex Imaginary Software, Ltd. 188221345SdimOur first step is to call @code{send-pr}. It really doesn't matter 189221345Sdimwhether we use @code{send-pr} from the shell or from within Emacs. 190193326SedIndeed, if we use Emacs as a primary editor, calling @code{send-pr} from 191234982Sdimthe shell is likely to start @code{send-pr} in an Emacs buffer anyway. 192193326SedSo, since our company, @emph{Imaginary Software, Ltd.}, uses @sc{gnu} 193226633Sdimsoftware extensively, we're pretty familiar with Emacs, so from within 194243830SdimEmacs we type 195243830Sdim@smallexample 196221345SdimM-x send-pr 197243830Sdim@end smallexample 198243830Sdim@noindent 199263508Sdimand we're greeted with the following screen: 200263508Sdim 201243830Sdim@cindex default PR template 202221345Sdim@cindex example of a default template 203221345Sdim@cindex blank PR template 204263508Sdim@cindex @code{bifrabulator} 205221345Sdim@cartouche 206221345Sdim@smallexample 207221345SdimSEND-PR: -*- text -*- 208243830SdimSEND-PR: Lines starting with `SEND-PR' will be removed 209226633SdimSEND-PR: automatically as well as all comments (the text 210243830SdimSEND-PR: below enclosed in `<' and `>'). 211243830SdimSEND-PR: Please consult the manual if you are not sure 212221345SdimSEND-PR: how to fill out a problem report. 213221345SdimSEND-PR: 214226633SdimSEND-PR: Choose from the following categories: 215221345SdimSEND-PR: 216221345SdimSEND-PR: bfd binutils bison 217226633SdimSEND-PR: byacc clib config cvs diff 218193326SedSEND-PR: doc emacs flex g++ gas 219234353SdimSEND-PR: gcc gdb glob gprof grep 220193326SedSEND-PR: info ispell kerberos ld libg++ 221218893SdimSEND-PR: libiberty make makeinfo mas newlib 222234982SdimSEND-PR: other patch rcs readline send-pr 223193326SedSEND-PR: test texindex texinfo texinfo.tex 224193326SedSEND-PR: bifrabulator <---@emph{note: this one is fake} 225193326SedSEND-PR: 226193326SedTo: cygnus-bugs@@cygnus.com 227193326SedSubject: 228193326SedFrom: jeffrey@@imaginary.com 229193326SedReply-To: jeffrey@@imaginary.com 230198092SrdivackyX-send-pr-version: send-pr @value{VERSION} 231234982Sdim 232193326Sed>Submitter-Id: imaginary 233193326Sed>Originator: Jeffrey Osier 234193326Sed>Organization: 235234982SdimImaginary Software, Ltd. 236193326Sed>Confidential: <[ yes | no ] (one line)> 237234982Sdim>Synopsis: <synopsis of the problem (one line)> 238193326Sed>Severity: <[ non-critical | serious | critical ] (one line)> 239193326Sed>Priority: <[ low | medium | high ] (one line)> 240234982Sdim>Category: <name of the product (one line)> 241218893Sdim>Class: <[sw-bug|doc-bug|change-request|support](oneline)> 242226633Sdim>Release: <release number or tag (one line)> 243226633Sdim>Environment: 244218893Sdim <machine, os, target, libraries (multiple lines)> 245193326SedSystem: SunOS imaginary.com 4.1.1 1 sun4 246193326SedArchitecture: sun4 247234982Sdim 248193326Sed>Description: 249234982Sdim <precise description of the problem (multiple lines)> 250193326Sed>How-To-Repeat: 251193326Sed <code/input/activities to reproduce (multiple lines)> 252234982Sdim>Fix: 253193326Sed@iftex 254234982Sdim@hrule 255194179Sed@end iftex 256193326Sed-----Emacs: *send-pr* (send-pr Fill)----All------------------ 257193326Sed@iftex 258234982Sdim@hrule 259193326Sed@end iftex 260193326Sed>Category: other[] 261234982Sdim@end smallexample 262194179Sed@end cartouche 263193326Sed@page 264193326SedWe know from past experience that we need to set certain information into 265234982Sdimeach field, so we compile all the information we know about our problem. 266194179SedWe have some sample code which we know should work, even though it 267193326Seddoesn't, so we'll include that. Below is the completed PR; we send this 268193326Sedusing @kbd{C-c C-c}. (The comments have been truncated). 269234982Sdim 270194179Sed@cindex completed Problem Report 271193326Sed@cindex example of a completed PR 272193326Sed@cartouche 273234982Sdim@smallexample 274194179SedSEND-PR: Lines starting with `SEND-PR' will be removed 275193326SedSEND-PR: automatically as well as all comments (the text 276193326SedSEND-PR: @dots{} 277193326SedSEND-PR: 278234982SdimTo: cygnus-bugs@@cygnus.com 279193326SedSubject: bifrabulator routines don't match 280193326SedFrom: jeffrey@@imaginary.com 281218893SdimReply-To: jeffrey@@imaginary.com 282243830SdimX-send-pr-version: send-pr @value{VERSION} 283194179Sed 284193326Sed>Submitter-Id: imaginary 285193326Sed>Originator: Jeffrey Osier 286193326Sed>Organization: 287193326SedImaginary Software, Ltd. 288234982Sdim>Confidential: no 289221345Sdim>Synopsis: bifrabulator routines don't match 290221345Sdim>Severity: serious 291234982Sdim>Priority: medium 292234982Sdim>Category: bifrabulator 293234353Sdim>Class: sw-bug 294234353Sdim>Release: progressive-930101 295234982Sdim>Environment: 296234353SdimSystem: SunOS imaginary.com 4.1.1 1 sun4 297234353SdimArchitecture: sun4 (SPARC) 298234353Sdim 299234353Sdim>Description: 300234982Sdim the following code I fed into the bifrabulator came back 301234353Sdim with a strange error. apparently, the prestidigitation 302234353Sdim routine doesn't match with the whatsitsname in all cases. 303243830Sdim 304243830Sdim>How-To-Repeat: 305243830Sdim call the bifrabulator on the following code. 306243830Sdim @emph{code sample@dots{}} 307243830Sdim 308243830Sdim>Fix: 309243830Sdim@iftex 310243830Sdim@hrule 311243830Sdim@end iftex 312243830Sdim-----Emacs: *send-pr* (send-pr Fill)----All------------------ 313243830Sdim@iftex 314243830Sdim@hrule 315243830Sdim@end iftex 316243830SdimTo send the problem report use: C-c C-c 317243830Sdim@end smallexample 318243830Sdim@end cartouche 319243830Sdim 320243830SdimWe type @kbd{C-c C-c}, and off it goes. Now, we depend on Cygnus 321243830SdimSupport to figure out the answer to our problem. 322243830Sdim 323243830SdimSoon afterward, we get the following message from Cygnus: 324243830Sdim 325243830Sdim@smallexample 326243830Sdim@group 327243830SdimFrom: gnats (GNATS management) 328243830SdimSender: gnats-admin 329243830SdimReply-To: hacker@@cygnus.com 330263508SdimTo: jeffrey@@imaginary.com 331243830SdimSubject: Re: bifrabulator/1425: routines don't match 332243830Sdim 333243830SdimThank you very much for your problem report. 334243830SdimIt has the internal identification: g++/1425. 335243830SdimThe individual assigned to look at your bug is: hacker 336243830Sdim(F.B. Hacker) 337243830Sdim 338243830SdimCategory: bifrabulator 339249423SdimResponsible: hacker 340251662SdimSynopsis: bifrabulator routines don't match 341263508SdimArrival-Date: Sat Feb 30 03:12:55 1993 342251662Sdim@end group 343251662Sdim@end smallexample 344249423Sdim 345263508Sdim@noindent 346263508SdimThis is our receipt that the bug has been accepted and forwarded to the 347263508Sdimresponsible party. 348193326Sed 349193326Sed@noindent 350193326SedA while later, we get the analysis: 351193326Sed 352193326Sed@smallexample 353193326Sed@group 354194179SedTo: jeffrey@@imaginary.com 355194179SedFrom: hacker@@cygnus.com 356194179SedSubject: Re: bifrabulator/1425: routines don't match 357194179SedReply-To: hacker@@cygnus.com 358193326Sed 359263508SdimGot your message, Jeff. It seems that the bifrabulator was 360193326Sedconfusing the prestidigitation routines with the realitychecker 361198092Srdivackywhen lexically parsing the whatsitsname. 362243830Sdim 363193326SedI'm working on robustisizing the bifrabulator now. 364193326Sed 365221345SdimHow about lunch next week? 366234982Sdim-- 367221345SdimF.B. Hacker 368221345SdimCygnus Solutions, Sunnyvale, CA 408 542 9600 369226633Sdim#include <std-disclaimer.h> 370221345Sdim@end group 371221345Sdim@end smallexample 372221345Sdim 373221345Sdim@noindent 374221345SdimAbout the same time, we get another message from Cygnus. 375221345Sdim 376263508Sdim@cindex state change example 377221345Sdim@cindex example of a state change 378221345Sdim@smallexample 379249423Sdim@group 380221345SdimFrom: hacker@@cygnus.com 381226633SdimTo: jeffrey@@imaginary.com 382221345SdimSubject: Re: bifrabulator/1425: doesn't match prestidig 383221345SdimReply-To: hacker@@cygnus.com 384221345Sdim 385221345Sdim 386221345Sdim `F.B. Hacker' changed the state to `analyzed'. 387221345Sdim 388226633SdimState-Changed-From-To: open-analyzed 389221345SdimState-Changed-By: hacker 390234982SdimState-Changed-When: Fri Feb 31 1993 08:59:16 1993 391221345SdimState-Changed-Why: 392226633Sdim figured out the problem, working on a patch this afternoon 393221345Sdim-- 394221345SdimF.B. Hacker 395249423SdimCygnus Solutions, Sunnyvale, CA 408 542 9600 396221345Sdim#include <std-disclaimer.h> 397221345Sdim@end group 398234982Sdim@end smallexample 399221345Sdim 400221345Sdim@noindent 401221345SdimThe bug has now been analyzed, and Cygnus is working on a solution. 402221345Sdim 403221345Sdim@noindent 404221345SdimSometime later, we get more mail from F.B.: 405221345Sdim 406221345Sdim@smallexample 407221345Sdim@group 408221345SdimTo: jeffrey@@imaginary.com 409221345SdimFrom: hacker@@cygnus.com 410221345SdimSubject: Re: bifrabulator/1425: routines don't match 411221345SdimReply-To: hacker@@cygnus.com 412221345Sdim 413221345SdimThere's a patch now that you can ftp over and check out. 414221345Sdim 415221345SdimHey, that joke you sent me was great! The one about the 416221345Sdimstrings walking into a bar... my boss laughed for an hour! 417234982Sdim-- 418221345SdimF.B. Hacker 419243830SdimCygnus Solutions, Sunnyvale, CA 408 542 9600 420221345Sdim#include <std-disclaimer.h> 421221345Sdim@end group 422234982Sdim@end smallexample 423234353Sdim@sp 2 424221345Sdim@smallexample 425221345Sdim@group 426221345SdimFrom: hacker@@cygnus.com 427221345SdimTo: jeffrey@@imaginary.com 428221345SdimSubject: Re: bifrabulator/1425: doesn't match prestidig 429221345SdimReply-To: hacker@@cygnus.com 430221345Sdim 431221345Sdim 432221345Sdim `F.B. Hacker' changed the state to `feedback'. 433221345Sdim 434243830SdimState-Changed-From-To: analyzed-feedback 435221345SdimState-Changed-By: hacker 436221345SdimState-Changed-When: Fri Feb 31 1993 23:43:16 1993 437221345SdimState-Changed-Why: 438221345Sdim got the patch finished, notified Jeff at Imaginary Software 439221345Sdim-- 440221345SdimF.B. Hacker 441221345SdimCygnus Solutions, Sunnyvale, CA 408 542 9600 442221345Sdim#include <std-disclaimer.h> 443221345Sdim@end group 444221345Sdim@end smallexample 445221345Sdim 446221345Sdim@noindent 447221345SdimThe bug has gone into @dfn{feedback} status now, until we get the patch, 448221345Sdiminstall it and test it. When everything tests well, we can mail F.B. 449221345Sdimback and tell him the bug's been fixed, and he can change the state of 450221345Sdimthe PR from @dfn{feedback} to @dfn{closed}. 451221345Sdim 452221345SdimFollowing is a list of valid @samp{>Category:} entries that are 453221345Sdimsupported by Cygnus. 454221345Sdim 455221345Sdim@menu 456221345Sdim* Valid Categories:: 457234353Sdim@end menu 458221345Sdim 459221345Sdim@c FIXME - is this list up to date? 460221345Sdim@include categ.texi 461221345Sdim 462221345Sdim@node Installing send-pr 463221345Sdim@appendix Installing @code{send-pr} on your system 464234353Sdim@cindex installation 465221345Sdim 466221345SdimIf you receive @code{send-pr} as part of a larger software distribution, 467221345Sdimit probably gets installed when the full distribution is installed. If 468221345Sdimyou are using @sc{gnats} at your site as well, you must decide where 469221345Sdim@code{send-pr} sends Problem Reports by default; see @ref{default site,, 470221345SdimSetting a default @var{site}}. 471221345Sdim 472221345Sdim@menu 473221345Sdim* installation:: installing `send-pr' by itself 474221345Sdim* default site:: setting a default site 475221345Sdim@end menu 476234982Sdim 477221345Sdim@node installation 478221345Sdim@section Installing @code{send-pr} by itself 479243830Sdim@cindex installation procedure 480221345Sdim 481221345SdimInstall @code{send-pr} by following these steps (you may need 482221345Sdim@code{root} access in order to change the @file{aliases} file and to 483221345Sdiminstall @code{send-pr}): 484221345Sdim 485221345Sdim@itemize @bullet 486221345Sdim@item 487221345SdimUnpack the distribution into a directory which we refer to as 488221345Sdim@var{srcdir}. 489221345Sdim 490221345Sdim@item 491221345SdimEdit the file @file{Makefile} to reflect local conventions. 492221345SdimSpecifically, you should edit the variable @samp{prefix} to alter the 493221345Sdiminstallation location. The default is @file{/usr/local}. All files are 494234982Sdiminstalled under @samp{prefix} (see below). 495221345Sdim 496243830Sdim@item @emph{Run} 497221345Sdim@smallexample 498221345Sdimmake all install [ info ] [ install-info ] [ clean ] 499221345Sdim@end smallexample 500221345Sdim 501193326Sed@noindent 502193326SedThe targets mean the following: 503193326Sed 504193326Sed@table @code 505193326Sed@item all 506193326SedBuilds @code{send-pr} and @code{install-sid} 507234982Sdim 508193326Sed@item install 509193326SedInstalls the following: 510193326Sed 511193326Sed@table @code 512193326Sed@item install-sid 513193326Sed@itemx send-pr 514193326Sedinto @file{@var{prefix}/bin} 515193326Sed 516193326Sed@item send-pr.1 517193326Sedinto @file{@var{prefix}/man/man1} 518193326Sed 519263508Sdim@item @var{site} 520263508Sdimthe list of valid @var{categories} for the Support Site from which you 521263508Sdimreceived @code{send-pr}, installed as 522263508Sdim@w{@file{@var{prefix}/share/gnats/@var{site}}} 523263508Sdim 524193326Sed@item send-pr.el 525263508Sdiminto @w{@file{@var{prefix}/share/emacs/lisp}}@footnote{If your main Emacs 526263508Sdimlisp repository is in a different directory from this, substitute that 527263508Sdimdirectory for @w{@file{@var{prefix}/share/emacs/lisp}}.} 528263508Sdim@end table 529263508Sdim 530263508Sdim@item info (@emph{optional}) 531263508SdimBuilds @file{send-pr.info} from @file{send-pr.texi}@* 532263508Sdim@c FIXME - is this still true? 533263508Sdim(@file{send-pr.info} is included with this distribution) 534263508Sdim 535263508Sdim@item install-info (@emph{optional}) 536263508SdimInstalls @file{send-pr.info} into @w{@file{@var{prefix}/info}} 537263508Sdim 538263508Sdim@item clean (@emph{optional}) 539263508SdimRemoves all intermediary build files that can be rebuilt from source 540263508Sdimcode 541263508Sdim@end table 542263508Sdim 543263508Sdim@item 544263508SdimRun 545263508Sdim 546263508Sdim@smallexample 547263508Sdiminstall-sid @var{your-sid} 548263508Sdim@end smallexample 549193326Sed 550263508Sdim@noindent 551263508Sdimwhere @var{your-sid} is the identification code you received with 552263508Sdim@w{@code{send-pr}}. @code{send-pr} automatically inserts this value 553263508Sdiminto the template field @samp{>Submitter-Id:}. If you've downloaded 554193326Sed@code{send-pr} from the Net, use @samp{net} for this value. 555193326Sed 556193326Sed@item 557226633SdimPlace the following line in 558218893Sdim@w{@file{@var{prefix}/share/emacs/lisp/default.el}}, or instruct your 559218893Sdimusers to place the following line in their @file{.emacs} files: 560234982Sdim 561218893Sdim@smallexample 562234982Sdim(autoload 'send-pr "send-pr" "Submit a Problem Report." t) 563234982Sdim@end smallexample 564226633Sdim 565218893Sdim@item 566218893SdimCreate a mail alias for the Support Site from which you received 567193326Sed@code{send-pr}, and for every site with which you wish to use 568193326Sed@code{send-pr} to communicate. Each alias must have a suffix of 569193326Sed@samp{-gnats}. The Support Site(s) will provide the correct addresses 570193326Sedwhere these aliases should point. For instance, edit your mail aliases 571193326Sedfile to contain something like: 572193326Sed 573193326Sed@smallexample 574234982Sdim# support sites; for use with send-pr 575221345Sdimcygnus-gnats: bugs@@cygnus.com # Cygnus Solutions 576198092Srdivackybumblebee-gnats: bumblebugs@@bumblebee.com # Bumblebee Inc. 577193326Sedmycompany-gnats: bugs@@my.company.com (@emph{if you use @sc{gnats} locally}) 578193326Sed@end smallexample 579193326Sed 580193326Sed@code{send-pr} automatically searches for these aliases when you type 581193326Sed 582193326Sed@smallexample 583193326Sedsend-pr cygnus 584193326Sedsend-pr bumblebee 585193326Sedsend-pr @var{site}@dots{} 586193326Sed@end smallexample 587193326Sed 588193326Sed@noindent 589263508Sdim@code{send-pr} also uses @var{site} to determine the categories of 590198092Srdivackyproblems accepted by the site in question by looking in 591193326Sed 592193326Sed@smallexample 593212904Sdim@var{prefix}/share/gnats/@var{site} 594198092Srdivacky@end smallexample 595193326Sed 596193326Sed@end itemize 597193326Sed 598226633Sdim@node default site 599198092Srdivacky@section Setting a default @var{site} 600193326Sed@cindex default @var{site} 601224145Sdim@cindex setting a default @var{site} 602193326Sed 603221345Sdim@code{send-pr} is capable of sending Problem Reports to any number of 604221345SdimSupport Sites, using mail aliases which have @samp{-gnats} appended them. 605198092Srdivacky@code{send-pr} automatically appends the suffix, so that when you type 606198092Srdivacky 607210299Sed@smallexample 608226633Sdimsend-pr @var{site} 609226633Sdim@end smallexample 610198092Srdivacky 611226633Sdim@noindent 612200583Srdivackythe Problem Report goes to the address noted in the @file{aliases} file 613200583Srdivackyas @w{@samp{@var{site}-gnats}}. You can do this in the Emacs version of 614200583Srdivacky@code{send-pr} by invoking the program with 615200583Srdivacky 616226633Sdim@smallexample 617221345SdimC-u M-x send-pr 618221345Sdim@end smallexample 619193326Sed 620263508Sdim@noindent 621193326SedYou are prompted for @var{site}. 622193326Sed 623193326Sed@var{site} is also used to error-check the @samp{>Category:} field, as a 624193326Sedprecaution against sending mistaken information (and against sending 625193326Sedinformation to the wrong site). 626212904Sdim 627193326SedYou may also simply type 628193326Sed 629193326Sed@smallexample 630193326Sedsend-pr 631193326Sed@end smallexample 632193326Sed 633263508Sdim@noindent 634193326Sedfrom the shell (or @w{@samp{M-x send-pr}} in Emacs), and the Problem 635193326SedReport you generate will be sent to the @var{site}, which is usually the 636193326Sedsite from which you received your distribution of @w{@code{send-pr}}. 637226633SdimIf you use @sc{gnats} at your own organization, the default is usually 638200583Srdivackyyour local address for reporting problems. 639193326Sed 640218893SdimTo change this, simply edit the file @file{Makefile} before installing 641218893Sdimand change the line 642218893Sdim 643218893Sdim@smallexample 644218893SdimGNATS_SITE = @var{site} 645218893Sdim@end smallexample 646218893Sdim 647218893Sdim@noindent 648218893Sdimto reflect the site where you wish to send PRs by default. 649218893Sdim 650218893Sdim@c --------------------------------------------------------------- 651218893Sdim@node Index 652218893Sdim@unnumbered Index 653193326Sed 654226633Sdim@printindex cp 655212904Sdim 656212904Sdim@c --------------------------------------------------------------- 657212904Sdim@contents 658198092Srdivacky@bye 659193326Sed