From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Serge Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re:
Date: Tue, 16 Feb 2010 04:26:36 -0500 [thread overview]
Message-ID: <4B7A64CC.9090108@cs.columbia.edu> (raw)
In-Reply-To: <1266274696-23018-1-git-send-email-serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Series applied, thanks.
Oren.
Serge Hallyn wrote:
> We've currently got ns_exec both in user-cr and cr_tests. Let's
> give the user-cr version all features of the cr_tests one, and
> get rid of the cr_tests one.
>
> I'm also renaming it nsexec bc nsexecwp is stupid and ns_exec is
> annoying, whereas nsexec lets you type 'nse<tab>'.
>
>
next prev parent reply other threads:[~2010-02-16 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 22:58 (unknown), Serge Hallyn
[not found] ` <1266274696-23018-1-git-send-email-serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-15 22:58 ` [PATCH 1/3] rename and install nsexec Serge Hallyn
2010-02-15 22:58 ` [PATCH 2/3] ignore -eexist for mkdir of a cgroup Serge Hallyn
2010-02-15 22:58 ` [PATCH 3/3] nsexec: remount proc and devpts Serge Hallyn
[not found] ` <1266274696-23018-4-git-send-email-serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-16 11:38 ` Michael Tokarev
[not found] ` <4B7A83CB.4070009-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2010-02-16 14:19 ` Serge E. Hallyn
2010-02-16 0:35 ` your mail Matt Helsley
[not found] ` <20100216003531.GL3714-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-02-16 19:04 ` Sukadev Bhattiprolu
2010-02-16 9:26 ` Oren Laadan [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-30 23:55 Yuniya
2016-01-13 12:46 Adam Richter
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=4B7A64CC.9090108@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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