From: Kalle Valo <kvalo@kernel.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for v5.20
Date: Mon, 08 Aug 2022 16:45:12 +0300 [thread overview]
Message-ID: <87o7wun91z.fsf@kernel.org> (raw)
In-Reply-To: <Yu6qQHMoBzC4zprg@kernel.org> (Jarkko Sakkinen's message of "Sat, 6 Aug 2022 20:52:00 +0300")
Jarkko Sakkinen <jarkko@kernel.org> writes:
>> Odd, I haven't noticed any UTF-8 problems in my setup but Gnus/Emacs is
>> known to be picky. After some more investigation I noticed this in
>> Jarkko's email:
>>
>> Content-Type: text/plain; charset=y
>>
>> I admit I'm not up to par with the latest cool stuff but that charset
>> can't be valid, right? :)
>
> I must have pressed 'y' and enter, instead of enter,
> when git send-email asked whether to use UTF-8 or
> something like that.
>
> Sorry about that :-) I don't recall doing that but
> that is what it looks like for me.
Hehe, that indeed sounds likely. Thanks, I was curious where that 'y'
came from :)
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-08-08 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 21:02 [GIT PULL] tpmdd updates for v5.20 Jarkko Sakkinen
2022-08-04 6:35 ` Kalle Valo
2022-08-04 12:01 ` James Bottomley
2022-08-05 5:43 ` Kalle Valo
2022-08-06 17:52 ` Jarkko Sakkinen
2022-08-06 17:53 ` Jarkko Sakkinen
2022-08-08 13:45 ` Kalle Valo [this message]
2022-08-09 16:57 ` Jarkko Sakkinen
2022-08-06 18:19 ` pr-tracker-bot
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=87o7wun91z.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--cc=torvalds@linux-foundation.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).