Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Cc: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>,
	Nathan Lynch <nathanl-V7BBcbaFuwjMbYB6QlFGEg@public.gmane.org>,
	Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
	Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Subject: linux-cr:  v23-rc1 pushed
Date: Mon, 10 Jan 2011 20:18:12 -0500	[thread overview]
Message-ID: <4D2BAFD4.1080400@cs.columbia.edu> (raw)

Folks,

I just pushed out a new v23-rc1 branch of linux-cr. This one is
rebased to 2.6.37, and contains nearly all the patches pulled
on v22-dev. I only gave it a brief test drive... feel free to 
throw all your ammo it.

Rebasing was fairly straightforward, but I'd feel more comfortable 
with more eyes looking at some code, specifically:

userns [Serge ?]
sockets [Dan ?]
cgroup_freezer [Matt ?]

I skipped PowerPC patches and ARM patches. Nathan, Christoffer -
can you take a look at those, respectively, and re-post to list ?

For the "final" v23, I'm hoping to add at least the logic for
unlinked files and inotify-and-friends; so now is probably a
good time to start circulating them ... (hint!)

There are some updates and fixes to user-cr too, mainly pulling
(and reworking) suka's old cleanup patches, and updating the
include files.

I also pulled and reworked Suka's patches for file-locks, and 
Nathan's patches for hugetlb - will post those seperately.

Happy New Year,

Oren.

             reply	other threads:[~2011-01-11  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11  1:18 Oren Laadan [this message]
     [not found] ` <4D2BAFD4.1080400-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-01-14  6:59   ` linux-cr: v23-rc1 pushed Sukadev Bhattiprolu
     [not found]     ` <20110114065911.GA11086-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2011-01-14 18:53       ` Oren Laadan
2011-01-27 13:23   ` Matt Helsley

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=4D2BAFD4.1080400@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=nathanl-V7BBcbaFuwjMbYB6QlFGEg@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=xemul-bzQdu9zFT3WakBO8gow8eQ@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