Index: head/en_US.ISO8859-1/articles/problem-reports/article.xml =================================================================== --- head/en_US.ISO8859-1/articles/problem-reports/article.xml +++ head/en_US.ISO8859-1/articles/problem-reports/article.xml @@ -1008,10 +1008,8 @@ Release: 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. + that you are running. This + needs to be filled in. @@ -1059,26 +1057,6 @@
Sending the Problem Report - If you are using &man.send-pr.1;: - - Once you are done filling out the template, have saved it, - and exit your editor, &man.send-pr.1; will prompt you with - s)end, e)dit or a)bort?. You can then hit - s to go ahead and submit the problem - report, e to restart the editor and - make further modifications, or a 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 to - &man.send-pr.1;: - - &prompt.user; send-pr -f ~/my-problem-report - - This will read the specified file, validate the contents, - strip comments and send it off. - If you are using the web form: @@ -1096,8 +1074,8 @@ cache. If this happens to you, your submission will be rejected and you may lose your work. - If you are unable to view images for any reason, and are - also unable to use &man.send-pr.1;, please accept our + 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 freebsd-bugbusters@FreeBSD.org. Index: head/en_US.ISO8859-1/books/dev-model/book.xml =================================================================== --- head/en_US.ISO8859-1/books/dev-model/book.xml +++ head/en_US.ISO8859-1/books/dev-model/book.xml @@ -1455,8 +1455,8 @@ 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. @@ -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, send-pr, to send - Problem Reports by email to the + and editing bug reports. The project uses its + web interface to send + Problem Reports to the projects central Bugzilla server. The committers also have web and command-line clients. Index: head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml +++ head/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml @@ -239,7 +239,7 @@ Submit the diff file using the web-based Problem - Report system or with &man.send-pr.1;. If using + Report system. If using the web form, enter a synopsis of [patch] short description of problem. Select the category Index: head/en_US.ISO8859-1/books/fdp-primer/translations/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/fdp-primer/translations/chapter.xml +++ head/en_US.ISO8859-1/books/fdp-primer/translations/chapter.xml @@ -289,7 +289,7 @@ &a.doceng;, and arrange to email the files when it is convenient. - Either way, you should use &man.send-pr.1; to submit a + 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 @@ 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. Thanks. Index: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml +++ head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml @@ -1112,8 +1112,8 @@ 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 WEB + web interface to it. Index: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml @@ -1859,7 +1859,7 @@ 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 Writing &os; Problem Reports. Index: head/en_US.ISO8859-1/htdocs/advocacy/myths.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/advocacy/myths.xml +++ head/en_US.ISO8859-1/htdocs/advocacy/myths.xml @@ -106,8 +106,8 @@ event.

  • Anyone can submit patches, bug reports, documentation, and - other contributions. They can do this by using the send-pr - program installed on their *BSD system, or by using a web based + other contributions. They can do this + by using a web based interface.

    Pointers to this system litter the documentation.

    • @@ -115,7 +115,7 @@

  • Not everyone can commit code changes to the *BSD code. You need to be a committer first. Typically, people are offered ``commit privs'' after they have made a few well-thought out - submissions to the project using send-pr or similar.

    + submissions to the project using Bugzilla or similar.

    This is identical to the Linux mechanism. Only one person is (notionally) allowed to change the Kernel, Linus. But specific areas Index: head/en_US.ISO8859-1/htdocs/gnome/docs/bugging.xml =================================================================== --- head/en_US.ISO8859-1/htdocs/gnome/docs/bugging.xml +++ head/en_US.ISO8859-1/htdocs/gnome/docs/bugging.xml @@ -63,10 +63,10 @@

  • Information specific for each type of breakage:

    • 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 http://freebsd-gnome.pastebin.com, - or send-pr(1) with attachment. Try to avoid sending any + href="http://freebsd-gnome.pastebin.com">http://freebsd-gnome.pastebin.com. + 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.