Re: CVS commit: src/usr.bin/chflags

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

On Wed, May 24, 2023 at 23:44:07 -0400, Jan Schaumann wrote:

> Valery Ushakov <uwe%stderr.spb.ru@localhost> wrote:
> > On Wed, May 24, 2023 at 22:33:17 +0000, Jan Schaumann wrote:
> 
> > > Briefly describe the 'arch' and 'nodump' flags.
> > 
> > What makes them special and why is that these two have to be described
> > here and not in chflags(2), where the flags are actually defined?
> 
> Unlike the other flags, they are not intuitive.  As
> they are exposed to the end-user (versus the
> programmer), it seems useful to describe them in
> section 1 of the manual pages.

This new paragraph is wedged right between the list of the options and
the continuation of that same paragraph that says that they can be
prefixed with "no".

A description of an obsolete flag right in the middle of the manpage
is a very poor narrative choice.

Calling nodump "not intuitive" is not intuitive.

Anyway, this change is strictly for the worse.  If you want to keep
these random tidbits of information, move them elsewhere, like HISTORY
section (which is probably the most appropriate place for the
obsolete, unused, compat-only msdos flag).

-uwe