Linux Security Modules development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Dr. Greg" <greg@enjellic.com>
Cc: Paul Moore <paul@paul-moore.com>, linux-security-module@vger.kernel.org
Subject: Re: TSEM feedback.
Date: Tue, 1 Aug 2023 07:55:29 -0500	[thread overview]
Message-ID: <20230801125529.GA915814@mail.hallyn.com> (raw)
In-Reply-To: <20230801105421.GA23193@wind.enjellic.com>

On Tue, Aug 01, 2023 at 05:54:21AM -0500, Dr. Greg wrote:
> On Mon, Jul 31, 2023 at 10:57:08AM -0400, Paul Moore wrote:
> 
> Good morning, I hope the day is starting well.
> 
> > On Mon, Jul 31, 2023 at 6:39???AM Dr. Greg <greg@enjellic.com> wrote:
> > >
> > > Good morning Paul, I hope this note finds your week starting well.
> > >
> > > We submitted the patches for the V2 release of TSEM three weeks ago.
> > >
> > > We received some feedback from Randy Dunlap on some documentations
> > > issues that we went on to address.
> > >
> > > Haven't heard any reflections from you.  Was just wondering if you
> > > were swamped or had possibly missed the submission?  We didn't include
> > > you as a copy on the notion that you didn't need two sets of patches
> > > landing in your inbox.
> 
> > If your mail hits the mail archive on lore.kernel.org, it is almost
> > a full guarantee that it has hit my inbox and/or the patchwork
> > instance I use to ensure nothing is missed.
> 
> So noted.
> 
> > As one would expect, it takes a good deal of time to review a patch
> > submission as large as TSEM, and the rather ornate language used in
> > the documentation only slows the process.
> 
> For whatever it is worth, as a group, we invested a considerable
> amount of time, over a period of now 8+ years, in refining the
> terminology and nomenclature embodied in that document.
> 
> I guess the only defense at hand is a variant on the alleged response
> by Austrian Emperor Joseph II to Mozart's "Die Entfuhrung aus dem
> Serail":
> 
> "It contains as many words, with appropriate ornateness, as was deemed
> necessary."

I cannot let such a golden opportunity pass to use
  https://www.youtube.com/watch?v=gA-sEfXOaEQ

  reply	other threads:[~2023-08-01 12:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 10:38 TSEM feedback Dr. Greg
2023-07-31 11:20 ` Bagas Sanjaya
2023-07-31 14:57 ` Paul Moore
2023-08-01 10:54   ` Dr. Greg
2023-08-01 12:55     ` Serge E. Hallyn [this message]
2023-08-01 18:49       ` Paul Moore

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=20230801125529.GA915814@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=greg@enjellic.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    /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