Subject: Re: (in)ability to send-pr
To: None <mouse@Collatz.McRCIM.McGill.EDU>
From: Gordon W. Ross <email@example.com>
Date: 03/12/1996 18:24:33
> Date: Tue, 12 Mar 1996 14:01:41 -0500
> From: der Mouse <mouse@Collatz.McRCIM.McGill.EDU>
> There seems to be this widespread idea that you can't send-pr except
> from a NetBSD box.
> This is a misconception. All my PRs are sent from my NeXT, at home,
> which is not (yet, sigh :) a NetBSD machine.
> send-pr is just a shell script. You need to copy a little other stuff,
> I seem to recall, but not much. And you need to tweak a pathname or
> two in the shell script. But it's not hard.
Actually, one does not even need the shell scripts. I just pull the
"blank form" below into emacs, edit as needed, and send the mail.
SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR: Please consult the send-pr man page `send-pr(1)' or the Texinfo
SEND-PR: manual if you are not sure how to fill out a problem report.
SEND-PR: Choose from the following categories:
SEND-PR: bin kern lib misc port-amiga
SEND-PR: port-hp300 port-i386 port-m68k port-mac port-pc532
SEND-PR: port-pmax port-sparc port-sun3 standards
<organization of PR author (multiple lines)>
>Confidential: <[ yes | no ] (one line)>
>Synopsis: <synopsis of the problem (one line)>
>Severity: <[ non-critical | serious | critical ] (one line)>
>Priority: <[ low | medium | high ] (one line)>
>Category: <name of the product (one line)>
>Class: <[ sw-bug | doc-bug | change-request | support ] (one line)>
>Release: <NetBSD-current source date>
<machine, os, target, libraries (multiple lines)>
<precise description of the problem (multiple lines)>
<code/input/activities to reproduce the problem (multiple lines)>
<how to correct or work around the problem, if known (multiple lines)>