From: Akira Yokosawa <akiyks@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org
Subject: Re: [cocci] [PATCH] coccinelle: update Coccinelle URL
Date: Tue, 10 Mar 2026 21:12:12 +0900 [thread overview]
Message-ID: <da719e3c-dd4d-4666-9d71-d02238a30482@gmail.com> (raw)
In-Reply-To: <c94cd15-2052-f746-ae38-304b4d838486@inria.fr>
On Tue, 10 Mar 2026 12:46:46 +0100 (CET), Julia Lawall wrote:
> On Tue, 10 Mar 2026, Akira Yokosawa wrote:
>
>> [removed most CCs]
>>
>> Hi Julia,
>>
>>> On Tue, 10 Mar 2026, Julia Lawall wrote:
>>>
>>>> The LIP6 URL no longer functions.
>>>>
>>>> Signed-off-by: Julia Lawall <Julia.Lawall@inria.fr>
>>>>
>>>> ---
>>>>
>>>> I used the UTF-8 encoding for the email.
>>>> Let me know if this was not the right choice.
>>>
>>> OK, this doesn't look good. Sorry for the noise. What is the proper
>>> encoding?
>>
>> Encoding itself looks good, but your patch has this in its header:
>>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=y
>> Content-Transfer-Encoding: 8bit
>>
>> , which should look like:
>>
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=UTF-8
>> Content-Transfer-Encoding: 8bit
>>
>> Didn't you say "y" to git-send-email's prompt of ...[UTF-8] ?
>
> Yes, I did. I thought that would select the default... Thanks for
> letting me know. Should I send it again, or is it ok as is?
I'd just resend with a proper charset.
Content-Type: text/plain; charset=y
would look confusing at best.
Thanks, Akira
>
> thanks,
> julia
>
>>
>> Thanks, Akira
>>
>>>
>>> thanks,
>>> julia
>>
prev parent reply other threads:[~2026-03-10 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 8:11 Julia Lawall
2026-03-10 8:14 ` [cocci] " Julia Lawall
2026-03-10 10:41 ` Akira Yokosawa
2026-03-10 11:46 ` Julia Lawall
2026-03-10 12:12 ` Akira Yokosawa [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=da719e3c-dd4d-4666-9d71-d02238a30482@gmail.com \
--to=akiyks@gmail.com \
--cc=julia.lawall@inria.fr \
--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