From: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: linux-cr: ckpt-v23-rc2 pushed
Date: Mon, 18 Apr 2011 15:33:43 -0500 [thread overview]
Message-ID: <20110418203343.GD18316@hallyn.com> (raw)
In-Reply-To: <20110418181803.GA3740-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
Quoting Matt Helsley (matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
> On Sat, Apr 16, 2011 at 08:59:13PM -0400, Oren Laadan wrote:
> > Hi,
> >
> > I finally merged all the recent patches and bug fixes, including hugetlb
> > and pids-as-objects. I pushed it as ckpt-v23-rc2 - both linux-cr and user-cr.
> > It applies on top of 2.6.37.
>
> Given that there have already been 3 -stable releases I was thinking it
> seems reasonable to move on to 2.6.38 for -rc3. What do you think?
That'd be nice. OTOH, the ckpt-v23-rc2 compiled fine for me both kernel
and userspace. I haven't had time to test yet - hopefully sometime this
week. Anyone is welcome to use the packages of course, at ppa:appcr/ppa.
next prev parent reply other threads:[~2011-04-18 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 0:59 linux-cr: ckpt-v23-rc2 pushed Oren Laadan
[not found] ` <4DAA3B61.10504-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-04-17 13:13 ` Serge E. Hallyn
[not found] ` <20110417131351.GA19709-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2011-04-24 6:02 ` Oren Laadan
2011-04-18 13:35 ` Dan Smith
[not found] ` <87ipubptr1.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2011-04-24 5:47 ` Oren Laadan
2011-04-18 18:18 ` Matt Helsley
[not found] ` <20110418181803.GA3740-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2011-04-18 20:33 ` Serge Hallyn [this message]
2011-04-24 6:04 ` Oren Laadan
[not found] ` <4DB3BD53.40102-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-04-24 9:34 ` Oren Laadan
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=20110418203343.GD18316@hallyn.com \
--to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=matthltc-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 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.