fdp/manual-pages: Nd argument should not be quoted
The Nd macro takes the rest of the line as an argument,
and is not shown quoted in any style guides.
fdp/manual-pages: Canonicalize SYNOPSIS
This follows changes made to the source tree to mdoc(7) and example(4).
All of our documentation on driver SYNOPSIS is now consistent.
Discussed with: arch@ (marc.info/?l=freebsd-arch&m=176782215606871)
Update EN-26:20.microcode to split 15.x and 14.x.
The 14.x patch required one additional commit to be included. Regenerate
and split the patches into major version specific patches.
Add Revision History to EN text and the two different patch URLs.
Reported by: David Cross
Approved by: so
documentation/copy-clipboard.js: Copy shell examples without the prompt
Shell blocks include the prompt ("% git remote -v") and the output of
the command, and the copy button handed all of it to the clipboard, so
the result could not be pasted into a shell. Asciidoctor callouts went
along with it, as "<1>" is rendered as markup inside the block.
Rebuild the copied text from the commands alone, reading the block with
the callout markup taken out, and keep the lines that carry a command
on: a trailing "\", "|" or "&&", and heredoc bodies up to their
delimiter.
Take "%", "$" and "#" for prompts, together with the host name they
sometimes carry, as in "freefall% gen-gitconfig.sh" in the Committer's
Guide or "ellington% ypcat -k netgroup" in the Handbook. A "#" is also
a comment and a common first character of output, so it only counts as
the root prompt where the block opens as root or gets there part way
through, as the Handbook example that runs "% su -" and goes on with "#
make install". The "# extended LDIF" header that ldapsearch(1) prints
[7 lines not shown]
internal/resources: Expand the commit bit and resources policy
Elaborate on how the core team delegates management of
repository-specific resources, such as commit bits, to the responsible
teams.
Add guidelines for suspending or revoking a commit bit: except where
circumstances justify immediate action, teams are expected to contact
the committer and provide an opportunity to address the problem before
acting, and to inform both the committer and the core team when a commit
bit is suspended or revoked.
Reviewed by: core (adrian, imp)
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D58830
