SEND-PR(1)

📦 in alpine 3.24

💅 SEND-PR(1) — the group-chat guide

okay so this is SEND-PR(1), from the General Commands Manual section, and bestie, if you've ever needed to yell at a support team in a structured, database-friendly way, this is your girl 🎀

✨ NAME ✨

send-pr — send a problem report (PR) to a central support site 🐛📨

🌸 SYNOPSIS 🌸

send-pr [ site ] [ -f problem-report ] [ -t mail-address ]
        [ -P ] [ -L ] [ -s severity ] [ -c address ]
        [ --request-id ] [ -v ]

💖 DESCRIPTION 💖

So send-pr is the tool you use to submit problem reports (PRs) to a central support site. Iconic. In most cases the correct site is just the default one — no need to overthink it. That site argument tells everyone which support site is responsible for the category of problem you're dealing with. Some sites might use a local address as their default. And where do site values come from? They're defined using aliases(5). iykyk 💅

Here's the vibe: send-pr invokes an editor on a problem report template (after trying to fill in some fields with reasonable default values, bless). When you exit the editor, send-pr sends the completed form to the Problem Report Management System (GNATS) at a central support site. Over at the support site, your PR gets assigned a unique number and is stored in the GNATS database according to its category and submitter-id. Then GNATS automatically replies with an acknowledgement, citing the category and the PR number. slay, automated ✨

Now, to make sure your PR actually gets handled promptly, it should contain your (unique) submitter-id and one of the available categories so everyone knows which problem area you're in. (Run send-pr -L to see a list of categories — yes, literally that easy 👑)

The send-pr 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 send-pr). If that hasn't been done, go see your system administrator for your submitter-id, or request one from your support site by invoking send-pr --request-id. And if your site doesn't distinguish between different user sites, or if you're not affiliated with the support site, use net for this field.

fr fr: the more precise your problem description and the more complete your information, the faster your support team can solve your problems. it's giving "help me help you" 🫶

🦋 OPTIONS 🦋

  • -f problem-report — specify a file (problem-report) which already contains a complete problem report. send-pr sends the contents of the file without invoking the editor. And if the value for problem-report is -, then send-pr reads from standard input. cute 🍓
  • -s severity — give the problem report the severity severity.
  • -t mail-address — change the mail address at the support site for problem reports. The default mail-address is the address used for the default site. Lowkey: use the site argument rather than this option in nearly all cases. 🙈
  • -c address — put address in the Cc: header of the message.
  • -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 send-pr version number.
Note: use send-pr to submit problem reports rather than mailing them directly. Using both the template and send-pr itself will help ensure all necessary information will reach the support site. no cap, this is the whole point 🎯

🌈 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). main character energy: pre-fill your own form 💅

🎀 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. one problem per PR, periodt ✨
  • 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 send-pr.info or the document Reporting Problems With send-pr 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. (big files? ask first, bestie 🌸)

⭐ 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 💀

💜 EMACS USER INTERFACE 💜

An Emacs user interface for send-pr with completion of field values is part of the send-pr distribution (invoked with M-x send-pr). See the file send-pr.info or the ASCII file INSTALL in the top level directory of the distribution for configuration and installation information. The Emacs LISP template file is send-pr-el.in and is installed as send-pr.el. emacs girlies, this one's for you 🌸

🌟 INSTALLATION AND CONFIGURATION 🌟

See send-pr.info or INSTALL for installation instructions. iykyk 📖

👑 SEE ALSO 👑

Reporting Problems Using send-pr (also installed as the GNU Info file send-pr.info).

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) — icons, honestly 🫶

🌸 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.

and that's the whole page, bestie ✨ This edition is version 3.96, dated February 1993 — vintage but still serving 💅🦋 go submit that PR, you got this 💖

📦 where this page comes from