- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1
builds.
- Update newvers.sh to reflect RC1.
- Update __FreeBSD_version to reflect 10.2.
- Update default pkg(8) configuration to use the quarterly branch.[1]

Discussed with: re, portmgr [1]
Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

MFC r256800: pathchk: Ensure bytes >= 128 are considered non-portable
characters.

This was not broken on architectures such as ARM where char is unsigned.

Also, remove the first non-portable character from the output. POSIX does
not require this, and printing the first byte may yield an invalid byte
sequence with UTF-8.

PR: 165988
Reported by: Nicolas Rachinsky
Relnotes: yes

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

pathchk: Add the new POSIX -P option.

This option checks for empty pathnames and components starting with '-'.
Our -p option also checks for the latter, which remains the case.

MFC after: 1 week

Sync program's usage() with manpage's SYNOPSIS.

Unbreak support for systems that have no limit on pathname length.

Noticed by: bde

Update pathchk to reflect the fact that 1003.1-2001 now includes the
trailing null byte in PATH_MAX and _POSIX_PATH_MAX.

PR: 46035

When stat(2) fails, put the name of the component it failed on in the
warning message as well as the path argument.

Add the pathchk utility, which checks pathnames for validity or
portability between POSIX systems.

Submitted by: Chuck Rouillard (manpage, initial implementation)