The send-pr(1) has been removed in FreeBSD 10, so remove it from most of the
documentation (books, articles, websites) unless there is an explicit or "obvious" reason. Do not touch old news articles, release notes, or the CGI scripts. Differential Revision: https://reviews.freebsd.org/D2380 Reviewed by: bjk
This commit is contained in:
Rene Ladan
parent
e008aa7051
commit
4d07437c99
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46642
8 changed files with 21 additions and 43 deletions
|
|
@ -1008,10 +1008,8 @@
|
|||
|
||||
<listitem>
|
||||
<para><emphasis>Release:</emphasis> The version of &os;
|
||||
that you are running. This is filled out automatically if
|
||||
you are using &man.send-pr.1; and need only be changed if
|
||||
you are sending a problem report from a different system
|
||||
than the one that exhibits the problem.</para>
|
||||
that you are running. This
|
||||
needs to be filled in.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -1059,26 +1057,6 @@
|
|||
<section xml:id="pr-writing-sending">
|
||||
<title>Sending the Problem Report</title>
|
||||
|
||||
<para>If you are using &man.send-pr.1;:</para>
|
||||
|
||||
<para>Once you are done filling out the template, have saved it,
|
||||
and exit your editor, &man.send-pr.1; will prompt you with
|
||||
<prompt>s)end, e)dit or a)bort?</prompt>. You can then hit
|
||||
<userinput>s</userinput> to go ahead and submit the problem
|
||||
report, <userinput>e</userinput> to restart the editor and
|
||||
make further modifications, or <userinput>a</userinput> to
|
||||
abort. If you choose the latter, your problem report will
|
||||
remain on disk (&man.send-pr.1; will tell you the filename
|
||||
before it terminates), so you can edit it at your leisure, or
|
||||
maybe transfer it to a system with better net connectivity,
|
||||
before sending it with the <option>-f</option> to
|
||||
&man.send-pr.1;:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>send-pr -f ~/my-problem-report</userinput></screen>
|
||||
|
||||
<para>This will read the specified file, validate the contents,
|
||||
strip comments and send it off.</para>
|
||||
|
||||
<para>If you are using the <link
|
||||
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web form</link>:</para>
|
||||
|
||||
|
|
@ -1096,8 +1074,8 @@
|
|||
cache. If this happens to you, your submission will be
|
||||
rejected and you may lose your work.</para>
|
||||
|
||||
<para>If you are unable to view images for any reason, and are
|
||||
also unable to use &man.send-pr.1;, please accept our
|
||||
<para>If you are unable to view images for any reason,
|
||||
please accept our
|
||||
apologies for the inconvenience and email your problem report
|
||||
to the bugbuster team at
|
||||
<email>freebsd-bugbusters@FreeBSD.org</email>.</para>
|
||||
|
|
|
|||
|
|
@ -1455,8 +1455,8 @@
|
|||
|
||||
<para>
|
||||
The difference when a contributor makes a code contribution is
|
||||
that he submits the code through the send-pr
|
||||
program. This report is picked up by the maintainer who
|
||||
that he submits the code through the Bugzilla
|
||||
interface. This report is picked up by the maintainer who
|
||||
reviews the code and commits it.
|
||||
</para>
|
||||
|
||||
|
|
@ -2074,9 +2074,9 @@
|
|||
Bugzilla is a maintenance database consisting of a set of tools to track bugs at a
|
||||
central site. It supports the bug tracking process for sending
|
||||
and handling bugs as well as querying and updating the database
|
||||
and editing bug reports. The project uses one of its many client
|
||||
interfaces, <quote>send-pr</quote>, to send
|
||||
<quote>Problem Reports</quote> by email to the
|
||||
and editing bug reports. The project uses its
|
||||
web interface to send
|
||||
<quote>Problem Reports</quote> to the
|
||||
projects central Bugzilla server. The committers also have web and
|
||||
command-line clients.
|
||||
</para>
|
||||
|
|
|
|||
|
|
@ -239,7 +239,7 @@
|
|||
<step>
|
||||
<para>Submit the diff file using the web-based
|
||||
<link xlink:href="&url.base;/support.html#gnats">Problem
|
||||
Report</link> system or with &man.send-pr.1;. If using
|
||||
Report</link> system. If using
|
||||
the web form, enter a synopsis of
|
||||
<emphasis>[patch] <replaceable>short description of
|
||||
problem</replaceable></emphasis>. Select the category
|
||||
|
|
|
|||
|
|
@ -289,7 +289,7 @@
|
|||
&a.doceng;, and arrange to email the files when it is
|
||||
convenient.</para>
|
||||
|
||||
<para>Either way, you should use &man.send-pr.1; to submit a
|
||||
<para>Either way, you should use Bugzilla to submit a
|
||||
report indicating that you have submitted the documentation.
|
||||
It would be very helpful if you could get other people to
|
||||
look over your translation and double check it first, since
|
||||
|
|
@ -350,7 +350,7 @@
|
|||
|
||||
<para>If you have country specific information, please submit
|
||||
it as a change to the English Handbook (using
|
||||
&man.send-pr.1;) and then translate the change back to your
|
||||
Bugzilla) and then translate the change back to your
|
||||
language in the translated Handbook.</para>
|
||||
|
||||
<para>Thanks.</para>
|
||||
|
|
|
|||
|
|
@ -1112,8 +1112,8 @@
|
|||
|
||||
<para>This is the mailing list for reporting bugs in &os;.
|
||||
Whenever possible, bugs should be submitted using the
|
||||
&man.send-pr.1; command or the <link
|
||||
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">WEB
|
||||
<link
|
||||
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web
|
||||
interface</link> to it.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
|
|||
|
|
@ -1859,7 +1859,7 @@ ports-mgmt/pkg
|
|||
</note>
|
||||
|
||||
<para>If there is no response to the email, use
|
||||
&man.send-pr.1; to submit a bug report using the
|
||||
Bugzilla to submit a bug report using the
|
||||
instructions in <link
|
||||
xlink:href="&url.articles.problem-reports;/article.html">Writing
|
||||
&os; Problem Reports</link>.</para>
|
||||
|
|
|
|||
|
|
@ -106,8 +106,8 @@
|
|||
event.</p></li>
|
||||
|
||||
<li><p>Anyone can submit patches, bug reports, documentation, and
|
||||
other contributions. They can do this by using the <tt>send-pr</tt>
|
||||
program installed on their *BSD system, or by using a web based
|
||||
other contributions. They can do this
|
||||
by using a web based
|
||||
interface.</p>
|
||||
|
||||
<p>Pointers to this system litter the documentation.</p></li>
|
||||
|
|
@ -115,7 +115,7 @@
|
|||
<li><p>Not everyone can commit code changes to the *BSD code. You
|
||||
need to be a <em>committer</em> first. Typically, people are offered
|
||||
``commit privs'' after they have made a few well-thought out
|
||||
submissions to the project using <tt>send-pr</tt> or similar.</p>
|
||||
submissions to the project using Bugzilla or similar.</p>
|
||||
|
||||
<p>This is identical to the Linux mechanism. Only one person is
|
||||
(notionally) allowed to change the Kernel, Linus. But specific areas
|
||||
|
|
|
|||
|
|
@ -63,10 +63,10 @@
|
|||
<li><p>Information specific for each type of breakage:</p>
|
||||
<ul>
|
||||
<li>If a port will not build, provide a full log of the
|
||||
unsuccessful build by either uploading it to any website,
|
||||
unsuccessful build by uploading it to any website or
|
||||
copy-and-paste to <a
|
||||
href="http://freebsd-gnome.pastebin.com">http://freebsd-gnome.pastebin.com</a>,
|
||||
or send-pr(1) with attachment. Try to avoid sending any
|
||||
href="http://freebsd-gnome.pastebin.com">http://freebsd-gnome.pastebin.com</a>.
|
||||
Try to avoid sending any
|
||||
attachments to the mailing list, because attachments sent
|
||||
to FreeBSD mailing lists are usually discarded by the
|
||||
mailing list software.</li>
|
||||
|
|
|
|||
Loading…
Reference in a new issue