e is =
when
they modified the switch logic to check for uppercase flags, but added the =
'J'
flag to the man page as lowercase 'j', and did not leave a reasoning on the=
se
differences in their commit message:
https://anonhg.netbsd.org/src/rev/e97bbfc29eff

Which is correct?  Both, technically!  Historically, lowercase letters were
first, in both NetBSD's man pages and source.  Then the source later got
updated to check the flags as uppercase values, but the man page still, to =
this
day, references lower case.  FreeBSD, on the other hand, is using uppercase
flags in its newsyslog.conf(5) man page and config examples, except for 'p',
but checks the flags as all lower case, which was the original logic from
NetBSD.  I assume that when the code for the 'p' flag was copied from NetBSD
and brought into FreeBSD, @eadler either didn't notice such a small nit, or
didn't care.  Both upper and lowercase flag values are technically valid,
because in either OS, the values are forced into one or the other case befo=
re
being checked.

If y'all want, I have no problem leaving the flag in the man page as-is as a
historical curiosity for someone to find again in the future.  Or, the patch
can be accepted and the flag changed to uppercase in FreeBSD's man page for
consistency with the other flags.

--=20
You are receiving this mail because:
You are the assignee for the bug.=