Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH] docs: format kernel-parameters -- as code
To:     Jonathan Corbet <corbet@lwn.net>, Stephen Kitt <steve@sk2.org>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20190627135938.3722-1-steve@sk2.org>
 <20190628091021.457d0301@lwn.net> <20190628203841.723ccd9c@heffalump.sk2.org>
 <20190628124804.5ce44f04@lwn.net>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <88c37575-2bee-03ff-970e-f4f77635da6e@infradead.org>
Date:   Fri, 28 Jun 2019 13:47:41 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <20190628124804.5ce44f04@lwn.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 6/28/19 11:48 AM, Jonathan Corbet wrote:
> On Fri, 28 Jun 2019 20:38:41 +0200
> Stephen Kitt <steve@sk2.org> wrote:
> 
>> Right, looking further shows a large number of places where -- is handled
>> incorrectly. The following patch disables this “smart” handling wholesale;
>> I’ll follow up (in the next few days) with patches to use real em- and
>> en-dashes where appropriate.
> 
> Thanks for figuring that out, it seems like the right thing to do.
> 
> Let's not worry about "real" dashes for now.  Not everybody welcomes
> non-ascii characters in the docs and, for dashes, it's something I deemed
> not worth fighting about.

Ack that.  Thanks.

-- 
~Randy