public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "Ahelenia Ziemiańska" <nabijaczleweli@nabijaczleweli.xyz>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH 2/2] filesystems.5: note ncpfs removal from kernel
Date: Thu, 17 Dec 2020 17:56:00 +0100	[thread overview]
Message-ID: <09db431f-0fac-f1d3-be94-ee2cc3b0921b@gmail.com> (raw)
In-Reply-To: <20201217164028.rphpncqtdavr27uy@tarta.nabijaczleweli.xyz>

Hi Ahelenia,

Please, could you append that into the first paragraph?
I feel 3 paragraphs is too much for a fs that has been already removed.

[
       ncpfs     is  a network filesystem that supports the NCP
                 protocol, used by Novell NetWare.  It was removed
                 from the kernel in 4.17.

                 To use ncpfs, you need special programs, which can
                 be found at ⟨ftp://linux01.gwdg.de/pub/ncpfs⟩.
]

Something like this.  This way, the "removed" notice is also closer to
the name.

Thanks,

Alex

P.S.: Sorry for not spotting this before :/

On 12/17/20 5:40 PM, Ahelenia Ziemiańska wrote:
> On Thu, Dec 17, 2020 at 05:23:06PM +0100, Alejandro Colomar (man-pages) wrote:
>> Could you remove the '-rc4' part from the version?
>> So that we show the first stable version where it was removed.
> Sure thing, see updated scissor-patch below:
> 
> -- >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>
> ---
>  man5/filesystems.5 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/man5/filesystems.5 b/man5/filesystems.5
> index 6ec2de9f0..1eda05b22 100644
> --- a/man5/filesystems.5
> +++ b/man5/filesystems.5
> @@ -160,6 +160,10 @@ To use
>  you need special programs, which can be found at
>  .UR ftp://ftp.gwdg.de\:/pub\:/linux\:/misc\:/ncpfs
>  .UE .
> +.IP
> +The
> +.B ncpfs
> +filesystem was removed from the kernel in 4.17.
>  .TP
>  .B nfs
>  is the network filesystem used to access disks located on remote computers.
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es

  reply	other threads:[~2020-12-17 16:56 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) [this message]
2020-12-17 17:59         ` Ahelenia Ziemiańska
2020-12-17 18:39           ` Alejandro Colomar (man-pages)
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=09db431f-0fac-f1d3-be94-ee2cc3b0921b@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