public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Stefan Puiu <stefan.puiu@gmail.com>
Cc: "Tomáš Golembiovský" <tgolembi@redhat.com>,
	linux-man@vger.kernel.org,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Subject: Re: [PATCH v2] abort: clarify consequences of calling abort
Date: Sat, 15 Jul 2023 17:44:26 +0200	[thread overview]
Message-ID: <f665f5c6-2b9f-8b22-6ec7-5b4b75e21204@kernel.org> (raw)
In-Reply-To: <CACKs7VB0mkKo4f6D9QkFmFuA2UZT24vQVV8L_ZsbNujNVGpaTg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1734 bytes --]

On 2023-07-12 12:45, Stefan Puiu wrote:
> Hi,
> 
> On Mon, Jul 10, 2023 at 6:41 PM G. Branden Robinson
> <g.branden.robinson@gmail.com> wrote:
>>
>>
>> At 2023-07-10T15:59:28+0200, Tomáš Golembiovský wrote:
>>
>> I believe Alex's preference in the Linux man-pages project is to
>> document what is actually implemented, not to repeat normative language
>> (paraphrased or not) from the POSIX standard.
>>
>> So glibc should be tested to verify the behavior it actually exhibits,
>> and the language above then updated to describe that, noting any
>> deviation from POSIX's prescription.
> 
> At least when Michael Kerrisk was the man-pages maintainer, he would
> usually ask for a test program proving that the documentation change
> is correct and / or a pointer to the kernel / libc code, where the
> behavior could be (hopefully) inferred. I think this is valuable, it
> makes it easier to track why a certain change was made, and how the
> behavior was observed at that time. If running the same test case
> after X years yields a different behavior, it's clear the change that
> it triggered no longer stands. It's also fair, I think: the burden of
> proof is on the person suggesting the change.

Hi Stefan!

Thanks for pointing that out!  I can only agree with you, and
I try maintain that good tradition of Michael.

Cheers,
Alex

> 
> Just my 2 cents,
> Stefan.
> 
>>
>> The same can, optionally, be done for other libcs like musl.
>>
>> Alex, please correct me if I'm mistaken.

Hi Branden!

I won't correct you either ;)

Thanks!

>>
>> Regards,
>> Branden

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


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

      reply	other threads:[~2023-07-15 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 13:59 [PATCH v2] abort: clarify consequences of calling abort Tomáš Golembiovský
2023-07-10 15:21 ` G. Branden Robinson
2023-07-12  8:11   ` Tomáš Golembiovský
2023-07-12 10:45   ` Stefan Puiu
2023-07-15 15:44     ` Alejandro Colomar [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=f665f5c6-2b9f-8b22-6ec7-5b4b75e21204@kernel.org \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=stefan.puiu@gmail.com \
    --cc=tgolembi@redhat.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