public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
	groff@gnu.org
Subject: Re: man page width limit and example indentation (was: rseq(2) man page)
Date: Wed, 11 Jan 2023 09:31:32 -0600	[thread overview]
Message-ID: <20230111153132.jhvt77pcrvmcxtbe@illithid> (raw)
In-Reply-To: <52043c93-aa58-9725-c20d-9edc1baa9131@gmail.com>

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

At 2023-01-11T00:30:16+0100, Alejandro Colomar wrote:
> On 1/10/23 22:39, G. Branden Robinson wrote:
> > Well, some of it, I'm still trying to fix for 1.23.  I _still_ have not
> > heard back from Bertrand.  It's been two weeks.  I need to start
> > considering begging Werner to come out of retirement just long enough to
> > tag and push some tar archives.  :-O
> 
> You can't do it, right?  Or do you?

I can create the tag in Git, but I don't have a GPG public key that the
FSF recognizes as having a "maintainer" bit, so I cannot validly upload
a distribution archive to alpha.gnu.org.  Apart from signing issues, I
don't have authorization to upload there, or know the correct procedure.
Since this is an RC, I don't need to be on a whitelist (if one exists)
to email info-gnu, since only final releases are announced there.  The
plan was to announce RC2 to the groff list and the GNU platform-testers
list.

I suspect the only things that _strictly_ require an official GNU
maintainer are generation of the signature for the distribution archive,
and upload of that archive to alpha.gnu.org.

If I were in Bertrand or Werner's position, I would prefer to perform
the Git tagging and archive generation ("make dist" or preferably "make
distcheck") myself.  But AFAIK there's no _technical_ barrier to me
doing those things.  (I already "distcheck" before _every_ set of
commits I push.)  But in theory I could just hand either of them an
archive of 1.23.0.rc2 and say "trust me".

> Yep.  Now I understand.  So yeah, I never try to guess how much the
> page will take up on screen, and just check experimentally.

That's a sound approach.  Nevertheless I would like to make tbl(1)'s
output more predictable on terminals for all groff users.  That should
lower user frustration.

> You're right.  I don't remember what was the exact issue we had with
> it.  Anyway, .in just works so far. :)

I really like weaning man page authors off of *roff requests; I may have
to take another look at this issue someday.  :D

Regards,
Branden

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

  reply	other threads:[~2023-01-11 15:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 17:16 rseq(2) man page Mathieu Desnoyers
2023-01-06 17:22 ` Alejandro Colomar
2023-01-06 17:50   ` Alejandro Colomar
2023-01-06 20:57     ` Mathieu Desnoyers
2023-01-06 22:57       ` Alejandro Colomar
2023-01-10 16:54         ` Mathieu Desnoyers
2023-01-10 19:28           ` Alejandro Colomar
2023-01-10 19:57             ` Mathieu Desnoyers
2023-01-10 19:03         ` man page width limit and example indentation (was: rseq(2) man page) G. Branden Robinson
2023-01-10 20:29           ` Alejandro Colomar
2023-01-10 21:39             ` G. Branden Robinson
2023-01-10 23:30               ` Alejandro Colomar
2023-01-11 15:31                 ` G. Branden Robinson [this message]
2023-01-11 15:39           ` G. Branden Robinson
2023-01-06 18:49   ` rseq(2) man page Mathieu Desnoyers

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=20230111153132.jhvt77pcrvmcxtbe@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    /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