Re: [PATCH v2 0/9] intro.3, libc.7, ldconfig.8: Revise

["G. Branden Robinson" <g.branden.robinson@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]

Hi Alex,

At 2023-01-04T13:34:59+0100, Alejandro Colomar wrote:
> > v2:
> > 
> > * No longer migrates `PP` macros to `P`.
> > * No longer migrates ASCII "arrow" `->` to troff special character.
> I'd like this change, if you can apply it globally.  But we'll leave
> it for a separate patch set.

Yes.  I already chased it down.  "Globally" affects 2 pages.

There is more elaborate ASCII art in sched(7).  That can be made
relatively pretty with Unicode arrow characters; the four orthogonal
single-stemmed arrows even happen to have portable special character
identifiers going back to 1976 AT&T troff.

But I'm not sure about chewing that one off.  Using special character
escape sequences would make the source looked weirder and misaligned.
There's a way around that (the `tr` request) but that's a fairly chunky
breach of the "no *roff requests in man page sources) rule that Ingo
Schwarze and I try to hold to.

Still, it's worth thinking about whether you'd like to have pic(1)
diagrams in the Linux man-pages, with ASCII/Unicode-art fallbacks for
terminal devices.

> This more or less corresponds to what we call srcfix (although some might
> qualify as ffix; the ones you called imprecise).
[...]
> This more or less corresponds to what we call tfix.
[...]
> This more or less corresponds to what we call wfix.  wfix can englobe
> tfix normally.
[...]
> This more or less corresponds to what we call ffix.  It might be good
> to break such changes in two or three separate categories, although
> sometimes one needs the other, and it's simpler to just apply one
> patch that does all of them.

I will recast my characterizations in the commit messages.  I used to
know the above categories, but they bit-rotted in my brain due to my
feverish rush to get groff 1.23 ready.  Context switches are expensive
in meatspace, too...

Do you continue to practice Michael's indifference to Git's first-line
"limit" to commit messages?  I have some pending patches that look like
this.

commit ab218d9f02bcfb9d6c7c127ed90c9a8c34cd8ba5
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date:   Wed Jan 4 02:31:37 2023 -0600

    adjtimex.2, eventfd.2, mmap2.2, perf_event_open.2, quotactl.2, shmget.2, times.2, drand48.3, ldexp.3, random.3, tgamma.3, proc.5, mount_namespaces.7, random.7, sched.7, tcp.7, udplite.7, units.7, unix.7, utf-8.7: srcfix

    Use correct *roff special character for hat/caret/circumflex accent.

    Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]