From: Steve Lawrence <slawrence@tresys.com>
To: Lukas Vrabec <lvrabec@redhat.com>, <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 1/2] Add description of missing newrole parameter -p in newrole man page.
Date: Tue, 12 Jan 2016 08:51:59 -0500 [thread overview]
Message-ID: <569504FF.9070306@tresys.com> (raw)
In-Reply-To: <1452504641-26411-1-git-send-email-lvrabec@redhat.com>
On 01/11/2016 04:30 AM, Lukas Vrabec wrote:
> Signed-off-by: Lukas Vrabec <lvrabec@redhat.com>
I fixed a minor typo in this patch. Otherwise looks good. Both patches
applied. Thanks!
> ---
> policycoreutils/newrole/newrole.1 | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/policycoreutils/newrole/newrole.1 b/policycoreutils/newrole/newrole.1
> index c47bc52..3bd57e7 100644
> --- a/policycoreutils/newrole/newrole.1
> +++ b/policycoreutils/newrole/newrole.1
> @@ -8,6 +8,7 @@ newrole \- run a shell with a new SELinux role
> [\fB-t\fR|\fB--type\fR]
> \fITYPE\fR
> [\fB-l\fR|\fB--level\fR]
> +[\fB-p\fR|\fB--preserve-environment\fR]
> \fILEVEL\fR [-- [\fIARGS\fR]...]
> .SH DESCRIPTION
> .PP
> @@ -38,7 +39,12 @@ specified by
> If
> \fILEVEL\fR
> is a range, the new context will have the sensitivity level and clearance
> -specified by that range.
> +specified by that range. If the
> +.B -p
> +or
> +.B --preserve-environment
> +option is specified, then shell with new SELinux context will preserve environment variables,
> +otherwise new minimal enviroment is created.
> .PP
> Additional arguments
> .I ARGS
>
prev parent reply other threads:[~2016-01-12 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 9:30 [PATCH 1/2] Add description of missing newrole parameter -p in newrole man page Lukas Vrabec
2016-01-11 9:30 ` [PATCH 2/2] Added missing descriptions for --*-key params in secon " Lukas Vrabec
2016-01-12 13:51 ` Steve Lawrence [this message]
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=569504FF.9070306@tresys.com \
--to=slawrence@tresys.com \
--cc=lvrabec@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.