From: Micah Morton <mortonm@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] SafeSetID changes for v6.0
Date: Wed, 3 Aug 2022 09:08:22 -0700 [thread overview]
Message-ID: <CAJ-EccOP4Yq4RSBSkA_71kagqvA=a+tUV63UbHWZVM2uqJMDFQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wim4B671BOPfxoXDSz0xfOruqoKCMQrjAX0R95PH5Wy4g@mail.gmail.com>
On Tue, Aug 2, 2022 at 3:20 PM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> On Mon, Aug 1, 2022 at 7:40 PM Micah Morton <mortonm@chromium.org> wrote:
> >
> > This pull request contains one commit that touches common kernel code,
> >
> > one that adds functionality internal to the SafeSetID LSM code, and a
> >
> > few other commits that only modify the SafeSetID LSM selftest.
> [...]
>
> What odd MUA do you use that causes this double-spaced text email?
>
> I can read it, but it really is a bit strange. It was all plain text,
> and marked as utf-8, and otherwise looked normal except for that
> double spacing.
>
> I get flashbacks to my "writing papers at university" days.
I know, it was ugly. I just switched laptops to a Mac and thought for
sure the mail message preview I was seeing in gmail after copy+paste
from a terminal window was just some weird scaling issue on my
external monitor or something. Sure enough the message was sent off
looking like a double spaced book report from 8th grade :)
I'll have to find what's going wrong with the copy+paste to gmail on
this particular device.
>
> Linus
next prev parent reply other threads:[~2022-08-03 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 2:42 [GIT PULL] SafeSetID changes for v6.0 Micah Morton
2022-08-02 22:19 ` Linus Torvalds
2022-08-03 16:08 ` Micah Morton [this message]
2022-08-02 22:29 ` 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='CAJ-EccOP4Yq4RSBSkA_71kagqvA=a+tUV63UbHWZVM2uqJMDFQ@mail.gmail.com' \
--to=mortonm@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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).