Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [nfs-utils PATCH 1/1] error.c: Put string for EOPNOTSUPP on
 single line
To:     Petr Vorel <pvorel@suse.cz>, linux-nfs@vger.kernel.org
References: <20200302140855.19453-1-pvorel@suse.cz>
From:   Steve Dickson <SteveD@RedHat.com>
Message-ID: <253ac076-7137-f172-900a-f87cfb99e384@RedHat.com>
Date:   Fri, 27 Mar 2020 15:15:07 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200302140855.19453-1-pvorel@suse.cz>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk


On 3/2/20 9:08 AM, Petr Vorel wrote:
> to help people find it when search for common NFS error:
> mount.nfs: requested NFS version or transport protocol is not supported
> 
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Committed... (tag: nfs-utils-2-4-4-rc2)

steved.

> ---
>  utils/mount/error.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/utils/mount/error.c b/utils/mount/error.c
> index 986f0660..73295bf0 100644
> --- a/utils/mount/error.c
> +++ b/utils/mount/error.c
> @@ -210,8 +210,7 @@ void mount_error(const char *spec, const char *mount_point, int error)
>  		nfs_error(_("%s: an incorrect mount option was specified"), progname);
>  		break;
>  	case EOPNOTSUPP:
> -		nfs_error(_("%s: requested NFS version or transport"
> -				" protocol is not supported"),
> +		nfs_error(_("%s: requested NFS version or transport protocol is not supported"),
>  				progname);
>  		break;
>  	case ENOTDIR:
>