| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Architecture
MFC After: 3 days
|
|
|
|
|
| |
NetBSD, OpenBSD, and Android's Bionic number the clauses 1 through 3,
so follow suit to make comparison easier.
|
|
|
|
|
|
|
|
|
|
|
| |
bottom of the manpages and order them consistently.
GNU groff doesn't care about the ordering, and doesn't even mention
CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put
them.
Found by: mdocml lint run
Reviewed by: ru
|
|
|
|
|
|
| |
PR: 141037
Submitted by: Jeremy Huddleston <jeremyhu@apple.com>
MFC after: 3 days
|
|
|
|
| |
Approved by: rwatson (mentor)
|
|
|
|
|
|
| |
clause.
# If I've done so improperly on a file, please let me know.
|
| |
|
| |
|
|
|
|
|
|
|
| |
concatenation and copy functions using the '__restrict' macro.
This is to satisfy IEEE Std 1003-1.2001.
- Use ANSI-C function definitions.
- Add the 'restrict' keyword to the manual pages, too.
|
|
|
|
| |
Stop abusing the .%J macro for where the .Pa macro should have been used.
|
|
|
|
|
|
|
|
|
| |
the first revision of strcpy(3)'s section is included, but should be
removed as the Security Architecture document is committed and
completed.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
| |
|
| |
|
| |
|
|
|
|
| |
More libraries manpages updates following.
|
|
|
|
| |
Inspired by: NetBSD commit message describing this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
|
|
| |
bytes are copied to the destination string. Closes PR#1000.
Submitted by: Dave Glowacki <dglo@ssec.wisc.edu>
|
|
|