From: Rahul Sandhu <nvraxn@posteo.uk>
To: Petr Lautrbach <lautrbach@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: HEADS UP: SELinux Userspace 3.11-rc1 release coming soon and code reformat
Date: Mon, 01 Jun 2026 17:00:50 +0000 [thread overview]
Message-ID: <86o6huxkjm.fsf@posteo.uk> (raw)
In-Reply-To: <87qzmq5iia.fsf@redhat.com> (Petr Lautrbach's message of "Mon, 01 Jun 2026 18:32:13 +0200")
On Mon Jun 01, 2026 at 05:32 PM BST, Petr Lautrbach wrote:
> 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
Hi Petr,
Would it be possible to merge in my patches[1][2][3] pertaining to the
various compiler bugs[4] for 3.11?
[1] https://lore.kernel.org/selinux/CAP+JOzRB=2-jSQaSVjVQ12YHb5yTM71yPrXmFDDG_FiaQaT3TQ@mail.gmail.com/T/#u
[2] https://lore.kernel.org/selinux/20260531054519.650723-2-nvraxn@posteo.uk/T/#u
[3] https://lore.kernel.org/selinux/20260531184111.691569-2-nvraxn@posteo.uk/T/#u
[4] https://lore.kernel.org/selinux/CAP+JOzQe8Mr9X=mV263-g0dr4VKM2kpqKQ_X1bg+Es8oXoUZYw@mail.gmail.com/T/#u
--
Rahul Sandhu
next prev parent reply other threads:[~2026-06-01 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 16:32 HEADS UP: SELinux Userspace 3.11-rc1 release coming soon and code reformat Petr Lautrbach
2026-06-01 17:00 ` Rahul Sandhu [this message]
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=86o6huxkjm.fsf@posteo.uk \
--to=nvraxn@posteo.uk \
--cc=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