All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: selinux@vger.kernel.org
Subject: Release 3.3 or not?
Date: Wed, 20 Oct 2021 14:22:59 +0200	[thread overview]
Message-ID: <87a6j3khr0.fsf@redhat.com> (raw)

Hello,

2 weeks ago I wrote that I would like to release 3.3 if there's no big
change. But in the mean time some patchsets landed on mailing list, see
bellow. My question is: do we want to wait until they are merged or it's
ok to postpone them to 3.4 development? Please let me know.

* https://patchwork.kernel.org/project/selinux/list/?series=561273&state=*
libsepol: add fuzzer for reading binary policies
    
it was reviewed by Jim who requested some changes.

* https://patchwork.kernel.org/project/selinux/list/?series=566429
libsepol: do not pass NULL to memcpy

v2 with requested changes, waits for review


* https://patchwork.kernel.org/project/selinux/patch/20211015123100.15785-1-cgzones@googlemail.com/
libselinux: use dummy variable to silence glibc 2.34 warnings

reviewed by Nicolas, work in progress I guess


* https://patchwork.kernel.org/project/selinux/list/?series=566423&state=*
Parallel setfiles/restorecon 

3rd version of the patchset, waits for review



Petr


             reply	other threads:[~2021-10-20 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 12:22 Petr Lautrbach [this message]
2021-10-20 14:35 ` Release 3.3 or not? James Carter

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=87a6j3khr0.fsf@redhat.com \
    --to=plautrba@redhat.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 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.