From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] mls_mcs.md: Convert section to markdown
Date: Tue, 24 Nov 2020 23:33:26 -0500 [thread overview]
Message-ID: <CAHC9VhRoHbRNWTW-y9xrUcrgMH1YDPR9V5RgC6q_sc34m0As+g@mail.gmail.com> (raw)
In-Reply-To: <71112670492a57f244225d200c121f25e267fa44.camel@btinternet.com>
On Tue, Nov 24, 2020 at 7:26 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
> On Mon, 2020-11-23 at 18:06 -0500, Paul Moore wrote:
> > On Fri, Nov 20, 2020 at 6:38 AM Richard Haines
> > <richard_c_haines@btinternet.com> wrote:
> > >
> > > Add a TOC to aid navigation and converted to markdown.
> > >
> > > Reworked a table that required rewording some text.
> > >
> > > Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> > > ---
> > > RFC Change: Updated MLS/MCS text to reflect [1] comments.
> > >
> > > All Notebook sections should now be in markdown.
> > >
> > > [1]
> > > https://lore.kernel.org/selinux/80e38828-1473-5bc5-1b23-067cd242125a@gmail.com/
> > >
> > > src/mls_mcs.md | 411 ++++++++++++++++++++++++---------------------
> > > ----
> > > 1 file changed, 204 insertions(+), 207 deletions(-)
> >
> > Merged, thanks Richard.
> >
> > There are a few other small outstanding patches that I'm going to
> > look
> > at now, but what does everyone think: time for a new GH release of
> > the
> > notebook?
> >
>
> Seems reasonable now all in markdown. I did notice a couple of HTML
> <br's in title.md and the notebook-examples README.md files. Not sure
> if worth removing ??.
Let me take a look at those, perhaps I can clean those up without too
much problem ...
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2020-11-25 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 11:38 [PATCH] mls_mcs.md: Convert section to markdown Richard Haines
2020-11-23 23:06 ` Paul Moore
2020-11-24 12:26 ` Richard Haines
2020-11-25 4:33 ` Paul Moore [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=CAHC9VhRoHbRNWTW-y9xrUcrgMH1YDPR9V5RgC6q_sc34m0As+g@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).