All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <flihp@twobit.us>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: [meta-selinux] updates
Date: Sat, 27 Feb 2016 17:53:32 -0800	[thread overview]
Message-ID: <56D2531C.6040204@twobit.us> (raw)

Hello all,

I've made a pass back over the meta-selinux backlog and pulled in the
commits necessary to get master building again. Many thanks to those who
posted patches. The next thing I'll be focusing on is a second pass over
the backlog to pull in the remaining bits. Thanks for all of your patience.

I'm also realizing that we don't have a release branch for Jethro. Since
we've tracked releases in the past I figure this should be something we
consider taking on too. I don't imagine it will be a large task but I'll
be hacking up a prototype to confirm / disprove this theory. The
unfortunate bit is that I've pushed the patches necessary to get master
building which likely means that a Jethro branch will require reverting
commits to get older package versions or will need to be based on an
older commit with some likely cherry-picking of things from master.

Thoughts?

Thanks,
Philip


                 reply	other threads:[~2016-02-28  1:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56D2531C.6040204@twobit.us \
    --to=flihp@twobit.us \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.