linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: Add 'fexcept_t'
Date: Tue, 22 Sep 2020 22:05:18 +0200	[thread overview]
Message-ID: <3eccfa66-3711-df48-9beb-bfea87dfffae@gmail.com> (raw)
In-Reply-To: <42f8c77e-27a5-651c-9768-fa08d11e5ba2@gmail.com>

Hi Michael,

On 2020-09-22 21:57, Michael Kerrisk (man-pages) wrote:
 >
 > The previous sentence is rather hard to parse. What (other) part of
 > the sentence does "to provide auxiliary information" relate to.
 > I suggest splitting the sentence in two and rewording.
 >
 >
 >> +A floating-point control mode is a system variable whose
 >
 > You suddenly introduce "floating-point control mode" here.
 > How does it relate to the preceding sentences? It's not clear.
 >
 > Going off to look at the standard... I see that actually your
 > sentences come pretty much straight from the standard. So, first, I
 > think the standard could have been clearer here. Second, and more
 > important, (for copyright reasons) we are on shaky ground if we just
 > lift whole passages from the standard.  The text does really need to
 > be in your own words. Can you come up with something?>
 > Alternatively, I guess we could explicitly quote the standard.
 > Something like
 >
 >      POSIX describes this type as follows:
 >      .RS
 >      .PP
 >      [The text]
 >      .RE

Yes.  A few patches ago I asked about that,
but you didn't answer to that specifically,
so I guessed that it was just fair use:

https://lore.kernel.org/linux-man/6dc80c25-85bf-925c-49c2-f79865027c0f@gmail.com/T/#mbfdcaf4fe625b4ff7ea90dc7396005fda1283612

But I guess explicitly quoting POSIX would be easy and better,
as you proposed.

I never used that type, so I wouldn't dare to describe it in my own words.

Thanks,

Alex

  reply	other threads:[~2020-09-22 20:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22 15:38 [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-22 15:38 ` [PATCH 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:17   ` [PATCH v2 1/2] system_data_types.7: Add 'fexcept_t' Alejandro Colomar
2020-09-23 13:31     ` Michael Kerrisk (man-pages)
2020-09-23 13:17   ` [PATCH v2 2/2] fexcept_t.3: New link to system_data_types(7) Alejandro Colomar
2020-09-23 13:31     ` Michael Kerrisk (man-pages)
2020-09-22 19:57 ` [PATCH 1/2] system_data_types.7: Add 'fexcept_t' Michael Kerrisk (man-pages)
2020-09-22 20:05   ` Alejandro Colomar [this message]
2020-09-22 20:14     ` Michael Kerrisk (man-pages)
2020-09-22 20:32       ` Alejandro Colomar
2020-09-22 20:37         ` Michael Kerrisk (man-pages)

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=3eccfa66-3711-df48-9beb-bfea87dfffae@gmail.com \
    --to=colomar.6.4.3@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).