No mail is sent. Displays a usage summary for send-pr . No mail is sent. This section contains instructions on what kinds of information to include and what kinds of mistakes to avoid. Include anything you would want to know if you were looking at the report from the other end.
Narratives are often useful, given a certain degree of restraint.
If a person responsible for a bug can see that A was executed, and then B and then C, knowing that sequence of events might trigger the realization of an intermediate step that was missing, or an extra step that might have changed the environment enough to cause a visible problem. This holds true across all problem reporting systems, for computer software or social injustice or motorcycle maintenance. Submit only one problem with each Problem Report. If you have multiple problems, use multiple PRs. This aids in tracking each problem and also in analyzing the problems associated with a given program.