From: Alejandro Colomar <alx.manpages@gmail.com>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Jakub Wilk <jwilk@jwilk.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH v3 1/3] timespec.3type: tv_nsec is impl-def-type, glibc llong not a bug
Date: Sun, 5 Feb 2023 17:09:33 +0100 [thread overview]
Message-ID: <d45af25b-e935-0d06-445c-89f2bb11f713@gmail.com> (raw)
In-Reply-To: <20230205154907.mqgw2e6m6u4yjsai@tarta.nabijaczleweli.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1232 bytes --]
On 2/5/23 16:49, наб wrote:
> On Sun, Feb 05, 2023 at 04:39:49PM +0100, Alejandro Colomar wrote:
>> I'll apply the following diff to your patch, if you agree:
>>
>> On 1/30/23 19:38, наб wrote:
>> diff --git a/man3type/timespec.3type b/man3type/timespec.3type
>> index 9b9e083bb..c3c69cfd2 100644
>> --- a/man3type/timespec.3type
>> +++ b/man3type/timespec.3type
>> @@ -16,7 +16,8 @@ .SH SYNOPSIS
>> .PP
>> .B struct timespec {
>> .BR " time_t tv_sec;" " /* Seconds */"
>> -.BR " /* ... */ tv_nsec;" " /* Nanoseconds [" 0 ", " 999\(aq999\(aq999 "] */"
>> +.RB " /* ... */" " tv_nsec;" \
>> +" /* Nanoseconds [" 0 ", " 999\[aq]999\[aq]999 "] */"
>> .B };
>> .EE
>> .SH DESCRIPTION
> Sure, go wild.
>
>> The /* ... */ should not be formatted, since it's not a literal (if you
>> found it formatted anywhere, that's a bug; please report).
> There's .B "#define EOF /* ... */" in man3const/EOF.3const,
> but besides that, all are in fR, yeah.
Thanks! Fixed. And I already applied the global change to use \[aq] and \[dq].
>
> наб
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-02-05 16:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 14:17 [PATCH 1/3] timespec.3type: tv_nsec is impl-def-type, glibc llong not a bug наб
2023-01-28 14:17 ` [PATCH 2/3] clock_getres.2, clock_getcpuclockid.3, pthread_getcpuclockid.3: fix tv_nsec formatting наб
2023-01-28 14:17 ` [PATCH 3/3] man2/clock_getres.2, man2/clock_nanosleep.2, man2/nanosleep.2, man2/timer_settime.2, man2/timerfd_create.2, man2/utimensat.2, man3/mq_send.3, man3/pthread_tryjoin_np.3, man3/sem_wait.3: standardise on "range [0, 999999999]" for tv_nsec наб
2023-01-29 15:48 ` [PATCH 1/3] timespec.3type: tv_nsec is impl-def-type, glibc llong not a bug Alejandro Colomar
2023-01-29 16:29 ` наб
2023-01-29 16:31 ` [PATCH v2 " наб
2023-01-29 16:41 ` Alejandro Colomar
2023-01-30 2:05 ` наб
2023-01-30 12:56 ` Alejandro Colomar
2023-01-29 16:31 ` [PATCH v2 2/3] clock_getres.2, clock_getcpuclockid.3, pthread_getcpuclockid.3: fix tv_nsec formatting наб
2023-01-29 16:31 ` [PATCH v2 3/3] man2/clock_getres.2, man2/clock_nanosleep.2, man2/nanosleep.2, man2/timer_settime.2, man2/timerfd_create.2, man2/utimensat.2, man3/mq_send.3, man3/pthread_tryjoin_np.3, man3/sem_wait.3: standardise on "range [0, 999\(aq999\(aq999]" for tv_nsec наб
2023-01-30 7:08 ` [PATCH 1/3] timespec.3type: tv_nsec is impl-def-type, glibc llong not a bug Jakub Wilk
2023-01-30 13:15 ` Alejandro Colomar
2023-01-30 13:50 ` G. Branden Robinson
2023-01-30 13:54 ` Alejandro Colomar
2023-01-30 19:47 ` Brian Inglis
2023-01-30 18:38 ` [PATCH v3 " наб
2023-02-05 15:39 ` Alejandro Colomar
2023-02-05 15:49 ` наб
2023-02-05 16:09 ` 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=d45af25b-e935-0d06-445c-89f2bb11f713@gmail.com \
--to=alx.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/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