*** send-pr/ChangeLog Fri Dec 12 21:11:01 1997 --- send-pr/ChangeLog Fri Dec 12 21:47:05 1997 *************** *** 1,3 **** --- 1,8 ---- + Fri Oct 31 17:00:00 1997 Abe Feldman + + * s-usage.texi: New node, "Submitting via e-mail" on how to submit + a problem report via direct e-mail. + Mon Aug 18 14:11:13 1997 Brendan Kehoe * Makefile.in (VERSION): Up to 3.104. I forgot to modify this for *** send-pr/s-usage.texi Fri Dec 12 21:11:01 1997 --- send-pr/s-usage.texi Fri Dec 12 21:45:45 1997 *************** *** 12,17 **** --- 12,18 ---- * using send-pr:: Creating new Problem Reports * send-pr in Emacs:: Using send-pr from within Emacs * send-pr from the shell:: Invoking send-pr from the shell + * Submitting via e-mail:: Submitting a Problem Report via direct e-mail * Helpful hints:: @end menu *************** *** 464,469 **** --- 465,497 ---- Displays a usage summary for @code{send-pr}. No mail is sent. @end table + @c ------------------------------------------------------------------------- + @node Submitting via e-mail + @section Submitting a Problem Report via direct e-mail + @cindex Direct e-mail + @cindex Submitting a PR via e-mail + In addition to using @code{send-pr}, there is another way to submit a problem + report. You can simply send an e-mail message to the support site. + + To do this, look at the address in the @samp{To:} field of the @code{send-pr} + template. When you send unformatted e-mail to this address, @sc{gnats} + processes the message as a new problem report, filling in as many fields from + defaults as it can: + + @table @code + @item Synopsis + The @samp{>Synopsis} field is filled in by the @samp{Subject:} header + + @item Description + All of the text in the body of the e-mail message is put into the + @samp{>Description} field. Each line of the text is indented by one space, + indicating that it is "quoted text" from the sender. + @end table + + Other fields, such as category, version, severity, etc. are set to default + values (if the @sc{gnats} administrator has set them). + + @c -------------------------------------------------------------------------- @node Helpful hints @section Helpful hints @cindex helpful hints