linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: management-style: Fix formatting of emphsized word
Date: Tue, 10 Mar 2020 11:32:44 -0600	[thread overview]
Message-ID: <20200310113244.527067de@lwn.net> (raw)
In-Reply-To: <20200303192113.20761-1-j.neuschaefer@gmx.net>

On Tue,  3 Mar 2020 20:21:12 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:

> Commit 7f2b3c65b9a1 ("Documentation/ManagementStyle: convert it to ReST
> markup") converted _underlined_ to *emphasized* words, but forgot about
> an underscore in this case.
> 
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
>  Documentation/process/management-style.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/process/management-style.rst b/Documentation/process/management-style.rst
> index 186753ff3d2d..dfbc69bf49d4 100644
> --- a/Documentation/process/management-style.rst
> +++ b/Documentation/process/management-style.rst
> @@ -227,7 +227,7 @@ incompetence will grudgingly admit that you at least didn't try to weasel
>  out of it.
> 
>  Then make the developer who really screwed up (if you can find them) know
> -**in_private** that they screwed up.  Not just so they can avoid it in the
> +**in private** that they screwed up.  Not just so they can avoid it in the
>  future, but so that they know they owe you one.  And, perhaps even more
>  importantly, they're also likely the person who can fix it.  Because, let's
>  face it, it sure ain't you.
> --
> 2.20.1
> 
Applied, thanks.

jon

      reply	other threads:[~2020-03-10 17:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 19:21 [PATCH] Documentation: management-style: Fix formatting of emphsized word Jonathan Neuschäfer
2020-03-10 17:32 ` 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=20200310113244.527067de@lwn.net \
    --to=corbet@lwn.net \
    --cc=j.neuschaefer@gmx.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).