public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, "Mark Wielaard" <mark@klomp.org>,
	"Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: man page base paragraph inset/indentation (was: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS)
Date: Sun, 18 Feb 2024 16:18:38 +0100	[thread overview]
Message-ID: <ZdIfz7lv2Dd9YaVG@debian> (raw)
In-Reply-To: <20240218141447.q34tghthp7d4llpg@illithid>

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

Hi Branden,

On Sun, Feb 18, 2024 at 08:14:47AM -0600, G. Branden Robinson wrote:
> This rendering parameter is now configurable, of course, to accommodate
> people who prefer the "old" one.  So when generating cat pages, doing
> diffs, or similar, you can pass the following option to GNU troff(1):
> 
> -rBP=7n

Nah, I like 5n.  I could use -RBP=7n in the build system for preventing
errors like this one for the time 1.24.0 is not a thing, to catch those
formatting issues with `make check`... but I think I prefer not.

Do you have in mind a date around which you intend to freeze for 1.24.0?
Mind the time it will take from a freeze to a release, so we get it in
Trixie this time.  :)

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.

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

  reply	other threads:[~2024-02-18 15:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12 12:07 [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Mark Wielaard
2024-02-18  1:09 ` Alejandro Colomar
2024-02-18 12:00   ` Mark Wielaard
2024-02-18 13:08     ` Alejandro Colomar
2024-02-18 14:14       ` man page base paragraph inset/indentation (was: [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS) G. Branden Robinson
2024-02-18 15:18         ` Alejandro Colomar [this message]
2024-02-18 16:36           ` groff 1.24 scheduling thoughts (was: man page base paragraph inset/indentation) G. Branden Robinson
2024-02-18 13:15     ` [PATCH v3] close_range.2: Add _GNU_SOURCE and unistd.h to SYNOPSIS Alejandro Colomar

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=ZdIfz7lv2Dd9YaVG@debian \
    --to=alx@kernel.org \
    --cc=ahajkova@redhat.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mark@klomp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox