Resubmitting a patch

Hi, I submitted a patch to this mailing list on December 15, 2016 which updated sv, runsv and svlogd by pulling in all the upstream changes and fixes to match version 2.1.2 of runit. I didn't receive any replies at that time, so what is the etiquette on this list for when this happens?

[PATCH 1/2] setpriv: new applet

Add a minimal 'setpriv' implementation supporting the NO_NEW_PRIVS bit. As upstream only supports long options (--nnp/--no-new-privs), A non-standard "-N" option is also added for the applet. Typical usage: $ busybox setpriv sudo uname Linux $ busybox setpriv --nnp sudo uname

[PATCH 0/2] new applet (setpriv) + unshare typo fix

Hello, I'd like to suggest adding a minimal 'setpriv' applet, based on upstream 'util-linux' package. The current implementation only supports turning on the NO_NEW_PRIVS bits and requires Linux kernel >= 3.5 . Also attach is a small typo fix for unshare's help screen. (This is my first busybox

[PATCH 2/2] unshare: fix help screen typo

"-r/--map-root-user" implies "-U/--user", not "-u/--uts". Signed-off-by: Assaf Gordon --- util-linux/unshare.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/util-linux/unshare.c b/util-linux/unshare.c index 52e8f14..44f7562 100644 ---