From 62371d2fa9b421dcd32a723df098eb0f75d95e06 Mon Sep 17 00:00:00 2001 From: Chris Rees Date: Wed, 3 Mar 2021 14:59:20 +0000 Subject: Update summary Bugzilla standard format for ports PR: docs/232816 Submitted by: salvadore Reviewed by: ygy Differential: https://reviews.freebsd.org/D23590 --- .../content/en/books/porters-handbook/quick-porting/chapter.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/en/books/porters-handbook/quick-porting/chapter.adoc b/documentation/content/en/books/porters-handbook/quick-porting/chapter.adoc index f8f3789e54..48d0cef894 100644 --- a/documentation/content/en/books/porters-handbook/quick-porting/chapter.adoc +++ b/documentation/content/en/books/porters-handbook/quick-porting/chapter.adoc @@ -257,7 +257,7 @@ Submit [.filename]#oneko.diff# with the https://bugs.freebsd.org/submit/[bug sub [NOTE] ==== -Giving a good description in the summary of the problem report makes the work of port committers a lot easier. We prefer something like "New port: _category/portname short description of the port_" for new ports. Using this scheme makes it easier and faster to begin the work of committing the new port. +Giving a good description in the summary of the problem report makes the work of port committers and triagers a lot easier. The expected format for new ports is "[NEW PORT] _category/portname short description of the port_" for new ports. Using this scheme makes it easier and faster to begin the work of committing the new port. ==== After submitting the port, please be patient. The time needed to include a new port in FreeBSD can vary from a few days to a few months. A simple search form of the Problem Report database can be searched at https://bugs.freebsd.org/bugzilla/query.cgi[]. -- cgit v1.2.3