From: Randy Dunlap <rdunlap@infradead.org>
To: Costa Shulyupin <costa.shul@redhat.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION PROCESS" <workflows@vger.kernel.org>
Subject: Re: [RFC PATCH] rework top page and organize toc on the sidebar
Date: Tue, 25 Jul 2023 23:03:00 -0700 [thread overview]
Message-ID: <26d59f6e-cc29-bcf4-d113-34c93804dea8@infradead.org> (raw)
In-Reply-To: <CADDUTFzKCrrBT=46F-08_EGrwMxVniDOgdkVr-DhGFTzS3DxOg@mail.gmail.com>
On 7/25/23 22:55, Costa Shulyupin wrote:
>> This patch is somewhat difficult to apply, as a result of:
>>> Content-Type: text/plain; charset=true
>
> This is caused by em dash in the context line:
> The following manuals are written for *users* of the kernel — those who are
>
> I haven't found how to fix it. Are there any tips?
Fix the email header or fix the em dash?
Did you use 'git send-email' for the patch? It seems to handle
UTF/UCS charsets AFAIK.
OTOH, any decent text editor can change the em dash to one or
two hyphens. (which I prefer)
cheers.
--
~Randy
next prev parent reply other threads:[~2023-07-26 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 19:31 Costa Shulyupin
2023-07-24 21:21 ` Jonathan Corbet
2023-07-25 3:04 ` Randy Dunlap
2023-07-26 5:55 ` Costa Shulyupin
2023-07-26 6:03 ` Randy Dunlap [this message]
2023-07-26 13:54 ` Jonathan Corbet
2023-07-26 18:49 ` [RFC PATCH v2] docs: rework "Working with the development community" Costa Shulyupin
2023-07-26 19:30 ` 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=26d59f6e-cc29-bcf4-d113-34c93804dea8@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@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