os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use correct syntax markup for shell

Browse source 
Approved by:	carlavilla
This commit is contained in:
Li-Wen Hsu 2021-03-14 20:08:55 +08:00
parent 55c95407aa
commit a9a9e66105
No known key found for this signature in database
GPG key ID: 8D7BCC7D012FD37E
666 changed files with 17924 additions and 17924 deletions
Download patch file Download diff file Expand all files Collapse all files

6
documentation/content/zh-tw/articles/pr-guidelines/_index.adoc
View file

@ -353,7 +353,7 @@ GNATS is picky about the format of a submitted bug report. This is why a lot of
When GNATS cannot deduce what to do with a problem report that reaches the database, it sets the responsible of the PR to `gnats-admin` and files it under the `pending` category. This is now a "misfiled" PR and will not appear in bug report listings, unless someone explicitly asks for a list of all the misfiled PRs. If you have access to the FreeBSD cluster machines, you can use `query-pr` to view a listing of PRs that have been misfiled:
[source,bash]
[source,shell]
....
% query-pr -x -q -r gnats-admin
52458 gnats-ad open serious medium Re: declaration clash f
@ -394,14 +394,14 @@ from the body of this PR to kern/12345
Searching with `query-pr` for the original PR, of which a misfiled followup is a reply, is as easy as running:
[source,bash]
[source,shell]
....
% query-pr -q -y "some text"
....
After you locate the original PR and the misfiled followups, use the `-F` option of `query-pr` to save the full text of all the relevant PRs in a UNIX(R) mailbox file, i.e.:
[source,bash]
[source,shell]
....
% query-pr -F 52458 52474 > mbox
....