From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 3/3] filesystems.5: wfix: ntfs: remove FAT comparison
Date: Tue, 29 Dec 2020 12:11:38 +0100 [thread overview]
Message-ID: <ee929f4a-7eca-e804-04b5-55e0fac1e13f@gmail.com> (raw)
In-Reply-To: <3354d6f2-be51-243d-d042-3a07bfb5df11@gmail.com>
[removed some CCs]
On 12/20/20 3:47 PM, Michael Kerrisk (man-pages) wrote:
> Hello Alex and наб
>
> On 12/18/20 4:30 PM, Alejandro Colomar wrote:
>> From: наб <nabijaczleweli@nabijaczleweli.xyz>
[...]
>>
>> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
>> Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
>
> Thanks. Patch applied. I cleaned up the commit message a little
> (removed leading white spaces, formatted to 66 columns as per the
> man-pages norm).
Hi Michael,
Where is that 66 col norm?
I've only found 75 for code in general (in man-pages(7)),
but not 66 for the commit msg.
Thanks,
Alex
>
> Cheers,
>
> Michael
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2020-12-29 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 15:30 [PATCH 0/3] filesystems.5: Update & wfix Alejandro Colomar
2020-12-18 15:30 ` [PATCH 1/3] filesystems.5: fix link to user space tooling for ncpfs Alejandro Colomar
2020-12-20 14:43 ` Michael Kerrisk (man-pages)
2020-12-18 15:30 ` [PATCH 2/3] filesystems.5: note ncpfs removal from kernel Alejandro Colomar
2020-12-20 14:44 ` Michael Kerrisk (man-pages)
2020-12-18 15:30 ` [PATCH 3/3] filesystems.5: wfix: ntfs: remove FAT comparison Alejandro Colomar
2020-12-20 14:47 ` Michael Kerrisk (man-pages)
2020-12-29 11:11 ` Alejandro Colomar (man-pages) [this message]
2020-12-29 20:00 ` 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=ee929f4a-7eca-e804-04b5-55e0fac1e13f@gmail.com \
--to=alx.manpages@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