From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>,
"Michael Kerrisk" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Subject: Re: [PATCH 2/2] filesystems.5: note ncpfs removal from kernel
Date: Thu, 17 Dec 2020 19:39:25 +0100 [thread overview]
Message-ID: <d24c6130-38aa-8087-f539-af361ab1d5ff@gmail.com> (raw)
In-Reply-To: <20201217175916.vx7fox46aqpzkcde@tarta.nabijaczleweli.xyz>
Hi Ahelenia,
On 12/17/20 6:59 PM, Ahelenia Ziemiańska wrote:
> On Thu, Dec 17, 2020 at 05:56:00PM +0100, Alejandro Colomar (man-pages) wrote:
>> Hi Ahelenia,
>>
>> Please, could you append that into the first paragraph?
> Sure, see updated scissor-patch below.
>
> I also broke the line above on the comma, because the alternative would
> be either
Thanks!
> is a network filesystem that supports the NCP protocol, used by
> Novell NetWare. It was removed from the kernel in 4.17.
> which sucks for reasons I assume obvious, or
> is a network filesystem that supports the NCP protocol, used by
> Novell NetWare.
> It was removed from the kernel in 4.17.
> which is three lines anyway.
>
> -- >8 --
> Subject: [PATCH 2/2] filesystems.5: note ncpfs removal from kernel
>
> Relevant Linux commits:
> * moved to staging in 1bb8155080c652c4853e6228f8f0d262b3049699
> (describe: v4.15-rc1-129-g1bb8155080c6) in Nov 2017,
> described as "broken" and "obsolete"
> * purged in bd32895c750bcd2b511bf93917bf7ae723e3d0b6
> (describe: v4.17-rc3-1010-gbd32895c750b) in Jun 2018,
> "since no one has complained or even noticed it was gone">
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
Patch applied.
Thanks for the detailed commit msg!
Cheers,
Alex
> ---
> man5/filesystems.5 | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/man5/filesystems.5 b/man5/filesystems.5
> index 6ec2de9f0..71be05230 100644
> --- a/man5/filesystems.5
> +++ b/man5/filesystems.5
> @@ -152,8 +152,9 @@ filenames can be no longer than 8 characters, followed by an
> optional period and 3 character extension.
> .TP
> .B ncpfs
> -is a network filesystem that supports the NCP protocol, used by
> -Novell NetWare.
> +is a network filesystem that supports the NCP protocol,
> +used by Novell NetWare.
> +It was was removed from the kernel in 4.17.
> .IP
> To use
> .BR ncpfs ,
>
--
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-17 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:27 [PATCH 1/2] filesystems.5: fix link to userspace tooling for ncpfs Ahelenia Ziemiańska
2020-12-17 15:27 ` [PATCH 2/2] filesystems.5: note ncpfs removal from kernel Ahelenia Ziemiańska
2020-12-17 16:23 ` Alejandro Colomar (man-pages)
2020-12-17 16:40 ` Ahelenia Ziemiańska
2020-12-17 16:56 ` Alejandro Colomar (man-pages)
2020-12-17 17:59 ` Ahelenia Ziemiańska
2020-12-17 18:39 ` Alejandro Colomar (man-pages) [this message]
2020-12-17 16:28 ` [PATCH 1/2] filesystems.5: fix link to userspace tooling for ncpfs Alejandro Colomar (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=d24c6130-38aa-8087-f539-af361ab1d5ff@gmail.com \
--to=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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