linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH v2] system_data_types.7: Move "Bugs" after "Notes", as man-pages(7) specifies
Date: Thu, 1 Oct 2020 17:18:55 +0200	[thread overview]
Message-ID: <a25e7070-d985-4a6e-3403-b161ba954e18@gmail.com> (raw)
In-Reply-To: <20201001142355.98424-1-colomar.6.4.3@gmail.com>

On 10/1/20 4:23 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
> ---
> 
> Hi,
> 
> I guess the patch before applies,
> but just in case, I rebased against what I think is your HEAD right now.
> You didn't upload it yet AFAICS, so I rebased my commits in the order
> you applied them.  I hope it works :)

Thanks! It does. And now I've just pushed.

Thanks,

Michael

>  man7/system_data_types.7 | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/man7/system_data_types.7 b/man7/system_data_types.7
> index abaf9e3cc..4645ed5f4 100644
> --- a/man7/system_data_types.7
> +++ b/man7/system_data_types.7
> @@ -40,13 +40,13 @@ system_data_types \- overview of system data types
>  .\"		* Description (no "Description" header)
>  .\"			A few lines describing the type.
>  .\"
> -.\"		* Bugs (if any)
> -.\"
>  .\"		* Conforming to (see NOTES)
>  .\"			Format: CXY and later; POSIX.1-XXXX and later.
>  .\"
>  .\"		* Notes (optional)
>  .\"
> +.\"		* Bugs (if any)
> +.\"
>  .\"		* See also
>  .\"------------------------------------- aiocb ------------------------/
>  .TP
> @@ -368,6 +368,9 @@ for printing
>  .I intmax_t
>  values.
>  .PP
> +Conforming to:
> +C99 and later; POSIX.1-2001 and later.
> +.PP
>  Bugs:
>  .I intmax_t
>  is not large enough to represent values of type
> @@ -378,9 +381,6 @@ is defined and
>  .I long long
>  is less than 128 bits wide.
>  .PP
> -Conforming to:
> -C99 and later; POSIX.1-2001 and later.
> -.PP
>  See also the
>  .I uintmax_t
>  type in this page.
> @@ -1309,6 +1309,9 @@ for printing
>  .I uintmax_t
>  values.
>  .PP
> +Conforming to:
> +C99 and later; POSIX.1-2001 and later.
> +.PP
>  Bugs:
>  .I uintmax_t
>  is not large enough to represent values of type
> @@ -1319,9 +1322,6 @@ is defined and
>  .I unsigned long long
>  is less than 128 bits wide.
>  .PP
> -Conforming to:
> -C99 and later; POSIX.1-2001 and later.
> -.PP
>  See also the
>  .I intmax_t
>  type in this page.
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2020-10-01 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 13:29 [PATCH] system_data_types.7: Move "Bugs" after "Notes", as man-pages(7) specifies Alejandro Colomar
2020-10-01 14:23 ` [PATCH v2] " Alejandro Colomar
2020-10-01 15:18   ` Michael Kerrisk (man-pages) [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=a25e7070-d985-4a6e-3403-b161ba954e18@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=colomar.6.4.3@gmail.com \
    --cc=linux-man@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).