From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: CRIU <criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [Announceme] Checkpoint-restore tool v0.8
Date: Fri, 18 Oct 2013 20:55:17 +0400 [thread overview]
Message-ID: <526167F5.1050906@parallels.com> (raw)
Hello, everyone!
I'm glad to announce the 8th release of the checkpoint-restore tool.
Though it was mostly bugfix release, we have added a couple of new
features.
You can find the changelog at http://criu.org/Download/criu/0.8
and get the sourced from http://download.openvz.org/criu/criu-0.8.tar.bz2
It doesn't require any _new_ kernel stuff, so you can run it on v3.11.
Have fun!
Thanks,
Pavel
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Emelyanov <xemul@parallels.com>
To: CRIU <criu@openvz.org>,
Containers <containers@lists.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Announceme] Checkpoint-restore tool v0.8
Date: Fri, 18 Oct 2013 20:55:17 +0400 [thread overview]
Message-ID: <526167F5.1050906@parallels.com> (raw)
Hello, everyone!
I'm glad to announce the 8th release of the checkpoint-restore tool.
Though it was mostly bugfix release, we have added a couple of new
features.
You can find the changelog at http://criu.org/Download/criu/0.8
and get the sourced from http://download.openvz.org/criu/criu-0.8.tar.bz2
It doesn't require any _new_ kernel stuff, so you can run it on v3.11.
Have fun!
Thanks,
Pavel
next reply other threads:[~2013-10-18 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 16:55 Pavel Emelyanov [this message]
2013-10-18 16:55 ` [Announceme] Checkpoint-restore tool v0.8 Pavel Emelyanov
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=526167F5.1050906@parallels.com \
--to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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.