From: Jonathan Corbet <corbet@lwn.net>
To: Andrew Klychkov <andrew.a.klychkov@gmail.com>
Cc: linux-kernel@vger.kernel.org, rdunlap@infradead.org
Subject: Re: [PATCH] (fixed after review) Documentation: fix typos found in admin-guide subdirectory
Date: Thu, 3 Dec 2020 16:12:53 -0700 [thread overview]
Message-ID: <20201203161253.1c00647c@lwn.net> (raw)
In-Reply-To: <20201203072247.GA41394@spblnx124.lan>
On Thu, 3 Dec 2020 10:22:47 +0300
Andrew Klychkov <andrew.a.klychkov@gmail.com> wrote:
> --- a/Documentation/admin-guide/cifs/usage.rst
> +++ b/Documentation/admin-guide/cifs/usage.rst
> @@ -115,7 +115,7 @@ later source tree in docs/manpages/mount.cifs.8
> Allowing User Unmounts
> ======================
>
> -To permit users to ummount directories that they have user mounted (see above),
> +To permit users to unmount directories that they have user mounted (see above),
> the utility umount.cifs may be used. It may be invoked directly, or if
> umount.cifs is placed in /sbin, umount can invoke the cifs umount helper
> (at least for most versions of the umount utility) for umount of cifs
> @@ -197,7 +197,7 @@ that is ignored by local server applications and non-cifs clients and that will
> not be traversed by the Samba server). This is opaque to the Linux client
> application using the cifs vfs. Absolute symlinks will work to Samba 3.0.5 or
> later, but only for remote clients using the CIFS Unix extensions, and will
> -be invisbile to Windows clients and typically will not affect local
> +be invisibile to Windows clients and typically will not affect local
So this one replaces one typo with another - perhaps not what you had in
mind :)
> applications running on the same server as Samba.
Thanks,
jon
next prev parent reply other threads:[~2020-12-03 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 7:22 Andrew Klychkov
2020-12-03 7:28 ` Randy Dunlap
2020-12-03 23:12 ` Jonathan Corbet [this message]
2020-12-04 7:02 Andrew Klychkov
2020-12-08 17:27 ` Jonathan Corbet
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=20201203161253.1c00647c@lwn.net \
--to=corbet@lwn.net \
--cc=andrew.a.klychkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
Powered by JetHome