From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
linux-man@vger.kernel.org,
"James K. Lowden" <jklowden@schemamania.org>
Subject: Re: syntax of options in man1
Date: Fri, 17 Jul 2026 19:23:55 +0200 [thread overview]
Message-ID: <alpkkFKmwAYZC7uU@devuan> (raw)
In-Reply-To: <20260717171509.4sdaukkhloy33lne@illithid>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
Hi Branden,
On 2026-07-17T12:15:09-0500, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2026-07-17T14:10:23+0200, Alejandro Colomar wrote:
> > On 2026-07-16T13:19:20-0400, Douglas McIlroy wrote:
> > > > I think there should be a separation between an introduction to
> > > > the entire system (maybe this could be intro(0)), and an
> > > > introduction to the first section of the manual (intro(1)).
> > >
> > > I agree. In the early days, at least, there was such a section,
> > > called "getting started". I like the idea of calling it intro(0).
> > > The very name suggests that there are more intro(.) pages. Elegant!
> >
> > Thanks! I've done the split already.
> >
> > commit 214f536963b0a108abc54b336d8ac21b4c9f1c7f
> > Author: Alejandro Colomar <alx@kernel.org>
> > Date: 2026-07-17 14:05:19 +0200
> >
> > man/man?/intro.[01]: Split part of intro(1) into a new intro(0)
> >
> > Let's keep intro(1) for introducing just the man1 section,
> > and move the more general introduction of the entire manual
> > to a new intro(0).
> >
> > Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
> > Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> I wonder if James K. Lowden's proposed "man-intro" document might be
> worth a second look at this time.
Would you mind bouncing the email to me? (If you have it.)
> https://lists.gnu.org/archive/html/groff/2021-05/msg00032.html
The thing is, I hate big-bang replacements. I'd like to see small
patches that can be reviewed on their own. If you would like to send
the most valuable pieces of it patch by patch, I'd like to have a look
at them.
Considering a full replacement of a manual page in a single commit is
something I don't enjoy.
Also, deciding on my own is boring and prone to mistakes. I'd prefer
a long discussion where we iterate over versions of patches.
Have a lovely day!
Alex
>
> Regards,
> Branden
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-17 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiXDGL658h1t_bstW0Z+MjjJfcNmcde-DA3QNOYKc0TTGg@mail.gmail.com>
2026-07-16 14:45 ` syntax of options in man1 Alejandro Colomar
2026-07-16 15:55 ` G. Branden Robinson
2026-07-16 16:20 ` Alejandro Colomar
2026-07-16 17:05 ` G. Branden Robinson
[not found] ` <CAKH6PiXx=WycAiPGti3LAAfpmDQExkcWsatXjOXpD=GdiMc0ng@mail.gmail.com>
2026-07-16 19:43 ` Douglas McIlroy
2026-07-17 12:10 ` Alejandro Colomar
2026-07-17 17:15 ` G. Branden Robinson
2026-07-17 17:23 ` Alejandro Colomar [this message]
2026-07-17 22:04 ` James K. Lowden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpkkFKmwAYZC7uU@devuan \
--to=alx@kernel.org \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=g.branden.robinson@gmail.com \
--cc=jklowden@schemamania.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.