From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: c/r: Add UTS support
Date: Mon, 06 Apr 2009 13:59:21 -0400 [thread overview]
Message-ID: <49DA42F9.10604@cs.columbia.edu> (raw)
In-Reply-To: <1239033956-25898-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Hmm.. I already integrated the previous version to the current
dev branch (see branch ckpt-v14-rc3-dev ; there are several
changed untested so I didn't release yet, but you can take a
look at the three corresponding patches.
BTW, in branch v14-rc3-dev of the userspace tool there is a
version of 'mktree' with the full algorithm for userspace task
creation.
Oren.
Dan Smith wrote:
> This is the latest version of my patch set with changes in support of
> feedback on version 6.
>
>
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>
next prev parent reply other threads:[~2009-04-06 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 16:05 c/r: Add UTS support Dan Smith
[not found] ` <1239033956-25898-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-04-06 16:05 ` [PATCH 1/3] Make cr_may_checkpoint_task() check each namespace individually Dan Smith
2009-04-06 16:05 ` [PATCH 2/3] c/r: Add UTS support (v7) Dan Smith
2009-04-06 16:05 ` [PATCH 3/3] Stub implementation of IPC namespace c/r (v3) Dan Smith
2009-04-06 17:59 ` Oren Laadan [this message]
[not found] ` <49DA42F9.10604-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2009-04-06 18:01 ` c/r: Add UTS support Dan Smith
-- strict thread matches above, loose matches on Subject: below --
2009-03-31 20:58 Dan Smith
2009-03-23 19:32 Dan Smith
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=49DA42F9.10604@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=danms-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