[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YvKR/a0BeD+QB4XF@kernel.org>
Date: Tue, 9 Aug 2022 19:57:33 +0300
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Kalle Valo <kvalo@...nel.org>
Cc: James Bottomley <James.Bottomley@...senpartnership.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Huewe <peterhuewe@....de>,
Jason Gunthorpe <jgg@...pe.ca>,
David Howells <dhowells@...hat.com>,
Paul Moore <paul@...l-moore.com>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
keyrings@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: [GIT PULL] tpmdd updates for v5.20
On Mon, Aug 08, 2022 at 04:45:12PM +0300, Kalle Valo wrote:
> Jarkko Sakkinen <jarkko@...nel.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 :)
Thanks for reporting this :-) Always good to sanity check, when
there is a visible inconsistency.
BR, Jarkko
Powered by blists - more mailing lists