diff options
author | Chris Rees <crees@FreeBSD.org> | 2021-03-03 14:59:20 +0000 |
---|---|---|
committer | Chris Rees <crees@FreeBSD.org> | 2021-03-03 14:59:20 +0000 |
commit | 62371d2fa9b421dcd32a723df098eb0f75d95e06 (patch) | |
tree | e742bcde46462b1cb50e0003cef99360423415ba | |
parent | 4cdb9554fc17f2e4ad78b1448f100bbf7f4504c3 (diff) |
Update summary Bugzilla standard format for ports
PR: docs/232816
Submitted by: salvadore
Reviewed by: ygy
Differential: https://reviews.freebsd.org/D23590
-rw-r--r-- | documentation/content/en/books/porters-handbook/quick-porting/chapter.adoc | 2 |
1 files changed, 1 insertions, 1 deletions
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[]. |