Replace query-pr.cgi and send-pr.html with their Bugzilla

equivalents.

Sponsored by:	The FreeBSD Foundation
This commit is contained in:
Glen Barber 2014-06-18 13:41:03 +00:00
parent 239be983b9
commit 4a4ba223dc
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=45075
14 changed files with 25 additions and 25 deletions

View file

@ -693,7 +693,7 @@ bde 2005-10-29 16:34:50 UTC
<formalpara>
<title>Report bugs upstream</title>
<para>If you notice bug in the FreeBSD code that you are
using, file a <link xlink:href="&url.base;/send-pr.html">bug
using, file a <link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">bug
report</link>. This step helps ensure that you do
not have to fix the bug the next time you take a code
drop from upstream.</para>

View file

@ -252,7 +252,7 @@
<para>If you find a bug or are submitting a specific change,
please report it using the &man.send-pr.1; program or its
<link xlink:href="&url.base;/send-pr.html">WEB-based
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">WEB-based
equivalent</link>. Try to fill-in each field of the bug
report. Unless they exceed 65KB, include any patches directly
in the report. If the patch is suitable to be applied to the

View file

@ -258,8 +258,8 @@
<listitem>
<para>Next, the searchable <link
xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">&os;
PR database</link> (GNATS). Unless the problem is recent
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">&os;
PR database</link> (Bugzilla). Unless the problem is recent
or obscure, there is a fair chance it has already been
reported.</para>
</listitem>
@ -498,7 +498,7 @@
a similar PR.</emphasis> Although this has already been
mentioned above, it bears repeating here. It only take a
minute or two to use the web-based search engine at <uri
xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query</uri>.
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">https://bugs.freebsd.org/bugzilla/query.cgi</uri>.
(Of course, everyone is guilty of forgetting to do this
now and then.)</para>
</listitem>
@ -562,7 +562,7 @@
display of the PR will be readable.</para>
<para>Similar considerations apply to use of the
<link xlink:href="&url.base;/send-pr.html"> web-based
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi"> web-based
PR submission form</link>. Note that cut-and-paste operations
can have their own side-effects on text formatting. In
certain cases it may be necessary to use &man.uuencode.1; to
@ -571,7 +571,7 @@
<para>Finally, if the submission is lengthy, prepare the work
offline so that nothing will be lost if there is a problem
submitting it. This can especially be a problem with the
<link xlink:href="&url.base;/send-pr.html">web
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web
form</link>.</para>
</section>
@ -723,7 +723,7 @@
<para>The next section describes fields that are common to both
the email interface and the
<link xlink:href="&url.base;/send-pr.html">web
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web
interface</link>:</para>
<itemizedlist>
@ -1161,7 +1161,7 @@
strip comments and send it off.</para>
<para>If you are using the <link
xlink:href="&url.base;/send-pr.html">web form</link>:</para>
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web form</link>:</para>
<para>Before you hit <literal>submit</literal>, you will need to
fill in a field containing text that is represented in image
@ -1207,7 +1207,7 @@
<listitem>
<para>The easiest way is to use the followup link on the
individual PR's web page, which you can reach from the <link
xlink:href="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query">PR
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">PR
search page</link>. Clicking on this link will bring up
an email window with the correct To: and Subject: lines
filled in (if your browser is configured to do this).</para>
@ -1329,7 +1329,7 @@
have happened is that the database index has gotten out of
synchronization with the database itself. The way that you can
test whether this has happened is to pull up the
<link xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi">view
<link xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">view
a single PR</link> page and see whether the PR shows up. If
it does, please notify the GNATS administrators at
<email>bugmeister@FreeBSD.org</email>. Note that there is a

View file

@ -165,7 +165,7 @@
</simpara>
</footnote>
through email, the &man.send-pr.1; application, or via the web
interface provided at <uri xlink:href="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</uri>.</para>
interface provided at <uri xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">https://bugs.freebsd.org/bugzilla/enter_bug.cgi</uri>.</para>
<para>To service our most conservative users, individual release
branches were introduced with &os;&nbsp;4.3.

View file

@ -593,13 +593,13 @@
<answer>
<para>The Problem Report database of all user change
requests may be queried by using our web-based PR <link
xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi?query">query</link>
xlink:href="https://bugs.freebsd.org/bugzilla/query.cgi">query</link>
interface.</para>
<para>The &man.send-pr.1; command can be used to submit
problem reports and change requests via electronic mail.
Alternatively, the <link
xlink:href="http://www.freebsd.org/send-pr.html">web-based
xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">web-based
problem report submission interface</link> can be used
to submit problem reports through a web browser.</para>

View file

@ -160,7 +160,7 @@
documentation tree.</para>
<para>If the diff file is to be submitted with the web
<quote><link xlink:href="&url.base;/send-pr.html">Submit a &os;
<quote><link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">Submit a &os;
problem report</link></quote> interface, add a
<filename>.txt</filename> extension to give the earnest and
simple-minded web form a clue that the contents are plain

View file

@ -1069,7 +1069,7 @@
<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="&url.base;/send-pr.html">WEB
<link xlink:href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">WEB
interface</link> to it.</para>
</listitem>
</varlistentry>

View file

@ -46,7 +46,7 @@ to the internet, these companies may offer what you need!</li>
<p>If your company supports a FreeBSD related product, service,
consulting, or support that should be added to this page, please
fill out a <a href="http://www.freebsd.org/send-pr.html">problem report</a>
fill out a <a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">problem report</a>
for category www. Submissions should contain a medium-sized
paragraph in length, describing your company.
Please note that the inclusion of vendors in our list does

View file

@ -65,7 +65,7 @@
<p>You should then let the Documentation Project know about it. The
correct way to do this is to use a command called <b>send-pr</b>, which
should be installed on your machine.
The <a href="&base;/send-pr.html">WWW problem report form</a> may also be used.</p>
The <a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">WWW problem report form</a> may also be used.</p>
<p>You do this so that your submission can be tracked. When you submit a PR
(Problem Report) it is assigned a unique number. One of the committers

View file

@ -1201,12 +1201,12 @@
<term>
<text>Submit a FreeBSD problem report</text>
<destination>&base;/send-pr.html</destination>
<destination>https://bugs.freebsd.org/bugzilla/enter_bug.cgi</destination>
</term>
<term>
<text>Bug report, submit</text>
<destination>&base;/send-pr.html</destination>
<destination>https://bugs.freebsd.org/bugzilla/enter_bug.cgi</destination>
</term>
<term>

View file

@ -125,8 +125,8 @@
<ul>
<li><a href="&base;/commercial/commercial.html">Vendors</a></li>
<li><a href="http://security.FreeBSD.org/">Security Information</a></li>
<li><a href="&cgibase;/query-pr-summary.cgi">Bug Reports</a></li>
<li><a href="&base;/send-pr.html">Submit Bug-report</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/query.cgi">Bug Reports</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">Submit Bug-report</a></li>
</ul>
</li>
</ul>

View file

@ -243,7 +243,7 @@
<p>FreeBSD's widespread popularity has spawned a number of user groups
around the world.</p>
<p>If you know of a FreeBSD user group not listed here,
please fill out a <a href="http://www.freebsd.org/send-pr.html">
please fill out a <a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">
problem report</a> for category www with the following information:</p>
<ol>
<li>A URL for the user group's website.</li>

View file

@ -180,7 +180,7 @@
</ul></li>
<li><a href="&base;/support/bugreports.html">Bug Reports</a>
<ul>
<li><a href="&base;/send-pr.html">Submit a Problem Report</a></li>
<li><a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">Submit a Problem Report</a></li>
</ul></li>
<li><a href="&base;/support/webresources.html">Web Resources</a></li>
</ul>

View file

@ -40,7 +40,7 @@
commercial listing into several sections. If your company
supports a FreeBSD-compatible product or service that should
be added to this page, please fill out a
<a href="http://www.FreeBSD.org/send-pr.html">problem report</a> for
<a href="https://bugs.freebsd.org/bugzilla/enter_bug.cgi">problem report</a> for
category www. Submissions should be in HTML and a medium-sized
paragraph in length.</p>