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 2/2] system_data_types.7: srcfix
Date: Fri, 25 Sep 2020 14:02:43 +0200 [thread overview]
Message-ID: <2a399b41-0fe7-4c38-c014-100728790f41@gmail.com> (raw)
In-Reply-To: <20200925112822.223218-1-colomar.6.4.3@gmail.com>
Hi Alex,
On 9/25/20 1:28 PM, Alejandro Colomar wrote:
> The contents of each type are a logic block that is indented as a block.
> They are not separate paragraphs that happen to be indented separately,
> but a set of continuous paragraphs, all in the same level,
> indented as a block from the list entry--the name of the type--.
> Therefore, it makes more sense to use block indentation, represented by
> .RS/.RE, rather than indenting each paragraph separately.
> That way it's also easier to further indent a separate paragraph inside
> a block, which happens for example in the case of float_t & double_t.
> It's simply much easier now to use .IP specifically in those cases where
> you want to indent just a single paragraph.
>
> Also added an ending separator comment line just after the last type.
>
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
Patch applied. Thanks!
> ---
>
> Hi Michael,
>
>
> On 2020-09-25 12:40, Michael Kerrisk (man-pages) wrote:
>> Just to confirm: I think I'm supposed to waiting on a revised
>> version of this patch, right? (This version of the patch doesn't
>> apply in my tree.)
>>
>> Thanks,
>>
>> Michael
>
> Right.
>
> It was somewhat complicated to fix the commits in the middle
> and rebase and then fix breakages and rebase again and fix more commits...
> I learned a lot of git today :)
:-}. Okay -- you can probably give me lessons!
Okay -- I declare a sync-point: as far as I know, I have nothing
outstanding from you. Let me know if I missed something.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-09-25 12:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 8:03 [PATCH 1/2] system_data_types.7: srcfix Alejandro Colomar
2020-09-25 8:03 ` [PATCH 2/2] " Alejandro Colomar
2020-09-25 10:40 ` Michael Kerrisk (man-pages)
2020-09-25 11:28 ` [PATCH v2 " Alejandro Colomar
2020-09-25 12:02 ` Michael Kerrisk (man-pages) [this message]
2020-09-25 12:46 ` Alejandro Colomar
2020-09-25 10:39 ` [PATCH 1/2] " Michael Kerrisk (man-pages)
2020-09-27 6:10 ` G. Branden Robinson
2020-09-27 20:24 ` Alejandro Colomar
2020-09-28 12:58 ` G. Branden Robinson
2020-09-28 13:29 ` Jakub Wilk
2020-09-28 13:40 ` G. Branden Robinson
2020-09-29 12:13 ` Michael Kerrisk (man-pages)
2020-09-30 10:12 ` G. Branden Robinson
2022-08-19 18:03 ` Jakub Wilk
2022-08-19 23:53 ` Alejandro Colomar
2022-08-20 5:43 ` G. Branden Robinson
2022-08-20 11:57 ` .TH 4th field (Was: [PATCH 1/2] system_data_types.7: srcfix) Alejandro Colomar
2022-08-20 12:20 ` G. Branden Robinson
2022-08-20 12:40 ` Alejandro Colomar
2022-08-20 13:04 ` Alejandro Colomar
2022-08-21 11:46 ` Alejandro Colomar
2022-08-24 13:22 ` Ingo Schwarze
2022-08-24 15:04 ` Alejandro Colomar
2022-08-24 17:12 ` Ingo Schwarze
2022-08-24 19:37 ` Alejandro Colomar
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=2a399b41-0fe7-4c38-c014-100728790f41@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.