linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Cc: mchehab@kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/binfmt-misc:Change backtick to apostrophe
Date: Mon, 27 Jul 2020 16:30:31 -0600	[thread overview]
Message-ID: <20200727163031.1579579b@lwn.net> (raw)
In-Reply-To: <20200724141209.32627-1-unixbhaskar@gmail.com>

On Fri, 24 Jul 2020 19:42:09 +0530
Bhaskar Chowdhury <unixbhaskar@gmail.com> wrote:

> This patch changed the backtick to apostrophe.
> 
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
> ---
> Jon,
>  I have changed as per your suggestion.Sorry about picking all the nits.
> 
>  Documentation/admin-guide/binfmt-misc.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/admin-guide/binfmt-misc.rst b/Documentation/admin-guide/binfmt-misc.rst
> index 0f5f82236853..e2abd08b985c 100644
> --- a/Documentation/admin-guide/binfmt-misc.rst
> +++ b/Documentation/admin-guide/binfmt-misc.rst
> @@ -83,7 +83,7 @@ Here is what the fields mean:
>        ``F`` - fix binary
>              The usual behaviour of binfmt_misc is to spawn the
>  	    binary lazily when the misc format file is invoked.  However,
> -	    this doesn`t work very well in the face of mount namespaces and
> +	    this doesn't work very well in the face of mount namespaces and

This doesn't apply to docs-next, probably because I didn't apply your
other patch.  Please send *one* patch that fixes it properly.

Thanks,

jon

      reply	other threads:[~2020-07-27 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 14:12 [PATCH] docs/binfmt-misc:Change backtick to apostrophe Bhaskar Chowdhury
2020-07-27 22:30 ` Jonathan Corbet [this message]

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=20200727163031.1579579b@lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).