From: Petr Lautrbach <lautrbach@redhat.com>
To: selinux@vger.kernel.org
Subject: HEADS UP: SELinux Userspace 3.11-rc1 release coming soon and code reformat
Date: Mon, 01 Jun 2026 18:32:13 +0200 [thread overview]
Message-ID: <87qzmq5iia.fsf@redhat.com> (raw)
Hi,
it's time of the year when we usually release new version of SELinux
Userspace and given the number of recent fixes, we'd like to release
3.11-rc1 during this week.
Also it's planned that the last commit before the release will be code
reformat using `make format` - this will effectivaly make all unmerged
patches unapplicable.
So if it's not urgent, please consider to stop sending new patches.
Thanks,
Petr
next reply other threads:[~2026-06-01 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 16:32 Petr Lautrbach [this message]
2026-06-01 17:00 ` HEADS UP: SELinux Userspace 3.11-rc1 release coming soon and code reformat Rahul Sandhu
2026-06-01 17:58 ` Stephen Smalley
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=87qzmq5iia.fsf@redhat.com \
--to=lautrbach@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox