public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tomáš Golembiovský" <tgolembi@redhat.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>,
	linux-man@vger.kernel.org, Stefan Puiu <stefan.puiu@gmail.com>
Subject: Re: [PATCH v4] abort: clarify consequences of calling abort
Date: Wed, 26 Jul 2023 14:56:07 +0200	[thread overview]
Message-ID: <ZMEX5_Mt_rm-QE0i@cremorrah> (raw)
In-Reply-To: <20230726113836.qery7vznhrm4hqdt@illithid>

Sure I will do that and resend.

Thanks,

    Tomas

On Wed, Jul 26, 2023 at 06:38:36AM -0500, G. Branden Robinson wrote:
> Hi Tomáš,
> 
> At 2023-07-20T17:38:01+0200, Tomáš Golembiovský wrote:
> > Clarify that atexit/on_exit are not called because those are called
> > only on normal process termination (as documented on their respective
> > manual pages).
> > 
> > Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>
> > Cc: Stefan Puiu <stefan.puiu@gmail.com>
> > Signed-off-by: Tomáš Golembiovský <tgolembi@redhat.com>
> [...]
> > +.BR atexit "(3) and " on_exit (3)
> 
> You might recast this line as:
> 
> .BR atexit (3)
> and
> .BR on_exit (3)
> 
> ...because it's (a) a little more readable (no quoted spaces) and (b) it
> be easily pattern-matched to migrate the man page cross references to
> the new `MR` macro in groff 1.23.0 (released at last), and for which I'm
> (slowly) working up a sed script.
> 
> There are plenty of special cases to handle, but stemming the influx of
> new ones will help.  :)
> 
> Regards,
> Branden



      reply	other threads:[~2023-07-26 12:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 15:38 [PATCH v4] abort: clarify consequences of calling abort Tomáš Golembiovský
2023-07-20 15:40 ` Tomáš Golembiovský
2023-07-26 11:38 ` G. Branden Robinson
2023-07-26 12:56   ` Tomáš Golembiovský [this message]

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=ZMEX5_Mt_rm-QE0i@cremorrah \
    --to=tgolembi@redhat.com \
    --cc=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=stefan.puiu@gmail.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