public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] execveat.2: srcfix
Date: Fri, 1 Jan 2021 12:43:44 +0100	[thread overview]
Message-ID: <72978fc8-4f7a-6ded-aa8a-96f9c03c6768@gmail.com> (raw)
In-Reply-To: <f306da07-e45d-2320-32a3-46f0955b3209@gmail.com>

Hi Alex,

On 1/1/21 12:29 AM, Alejandro Colomar (man-pages) wrote:
> 
> 
> On 12/31/20 7:55 PM, Alejandro Colomar (man-pages) wrote:
>> Hi Michael,
>>
[...]

> Hi Michael,
> 
> I've seen some of the 'ffix!!' problems are caused by a yet missing
> [.nf/.fi].

Yes.

> So when you finish the patch I guess they'll vanish.
> Still have a look at some of them, though, as there might be other causes.

Yes, thanks for catching those.

>> BTW, Why didn't you include man2?
> [...]
> 
>>>
>>> What do you think about the work-in-progess patch below? The following
>>> may be useful for review:
>>>
>>> for p in $(git grep -l 'SYN' man[3-8]); do 
>>>     echo "===================== $p"; man -l $p  2> /dev/null  | 
>>>         sed -n '/^SYNOP/,/DESCR/p' | sed '/Feat/,$d';
>>> done | less
> 
> I see now that the patch has changed man2, but the script above only
> shows man3 and above.  I guess those were the ones you had pending,
> right? :)

Yes.

> 
> Send me the next revision when you have it to have another look at it.

I pushed something now. Maybe we tweak it still a bit.

> Although the render looks weird on some cases because it's not yet
> finished, the diff looks good to me.

Okay.

Thanks,

Michael


-- 
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:[~2021-01-01 11:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-30 21:41 [PATCH] execveat.2: srcfix Alejandro Colomar
2020-12-30 22:27 ` Michael Kerrisk (man-pages)
2020-12-30 23:28   ` Alejandro Colomar (man-pages)
2020-12-31 10:06     ` Michael Kerrisk (man-pages)
2020-12-31 12:28       ` Alejandro Colomar (man-pages)
2020-12-31 15:26         ` Michael Kerrisk (man-pages)
2020-12-31 18:55           ` Alejandro Colomar (man-pages)
2020-12-31 23:29             ` Alejandro Colomar (man-pages)
2021-01-01 11:43               ` Michael Kerrisk (man-pages) [this message]
2021-01-01 11:41             ` Michael Kerrisk (man-pages)
2021-01-01 13:49               ` Alejandro Colomar (man-pages)
2021-01-01 22:29                 ` Michael Kerrisk (man-pages)
2021-01-02 16:03                   ` Alejandro Colomar (man-pages)
2021-01-02 19:59                     ` Michael Kerrisk (man-pages)
2021-01-02 21:40                       ` Alejandro Colomar (man-pages)
2021-01-03 12:11                         ` Michael Kerrisk (man-pages)
2021-01-04 12:59                           ` Alejandro Colomar (man-pages)
2021-01-04 13:21                             ` Michael Kerrisk (man-pages)
2021-02-02 17:43           ` Alejandro Colomar (man-pages)
2021-02-13 19:15             ` 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=72978fc8-4f7a-6ded-aa8a-96f9c03c6768@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@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