From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Sukadev Bhattiprolu
<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org,
Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>,
Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [PATCH 0/6][v3][lxc] Link LXC with USERCR
Date: Thu, 01 Apr 2010 19:36:32 -0400 [thread overview]
Message-ID: <4BB52E00.9010805@cs.columbia.edu> (raw)
In-Reply-To: <20100401163735.GA23231-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Sukadev Bhattiprolu wrote:
> Cedric Le Goater [clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org] wrote:
>> Hello Suka,
>>
>> On 04/01/2010 03:55 AM, Sukadev Bhattiprolu wrote:
>>
>>> Resending patches after fixing whitespace damage and the typo in
>>> configure.ac. Add a section to patch-0 (below) to describe the
>>> kernel build (commit-id, config tokens etc).
>> we plan to mergepatch 2,3,4 in lxc mainline real soon, maybe not as such,
>> but they won't be in the way anymore. For the moment, please keep 1,5,6 but
>> make it one patch. no need to resend them in a scattered mode.
>
> Ok. Can you apply 1,5,6 to a separate branch, say usercr-v1, so its easier
> for others to pull ? When I have some major changes I can resend the patches
> merged up to latest LXC and maybe we can then have usercr-v2 and so on.
>
>>> 1. Build C/R-enabled Linux kernel
>>>
>>> $ cd /root
>>>
>>> $ git-clone git://www.linux-cr.org/pub/git/linux-cr.git linux-cr
>>>
>>> $ cd linux-cr
>>>
>>> $ git-checkout ckpt-v20-dev
>>>
>>> I tested with commit 3522c57a9ec6f08a129a78322318abcb4467db28
>>> as HEAD.
>> we need to work on a better delivery scheme. I don't think a commit id is not
>> the most efficient way to dialog when integrating components. We'd rather use
>> a tarball or a patch on an identified kernel.
>
> Hmm, I thought we could just make a branch on the commit-id and apply
> any additional patches there and build.
>
> I will base it on a closed-release next time like ckpt-v20-rc1 rather
> than an open one like ckpt-v20-dev.
The stable and -rc versions are tagged with cr-vXX[-rcY].
For example, current version is cr-v21-rc2 (both linux-cr and user-cr)
Oren.
prev parent reply other threads:[~2010-04-01 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 1:55 [PATCH 0/6][v3][lxc] Link LXC with USERCR Sukadev Bhattiprolu
[not found] ` <20100401015503.GA25228-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-01 1:55 ` [PATCH 1/6][v3][lxc] Add --with-libcr configure option Sukadev Bhattiprolu
2010-04-01 1:55 ` [PATCH 2/6][v3][lxc] lxc_restart: Add --statefile option Sukadev Bhattiprolu
2010-04-01 1:56 ` [PATCH 3/6][v3][lxc] lxc_checkpoint: " Sukadev Bhattiprolu
2010-04-01 1:56 ` [PATCH 4/6][v3][lxc] Move get_init_pid() into checkpoint.c Sukadev Bhattiprolu
2010-04-01 1:56 ` [PATCH 5/6][v3][lxc] Hook up lxc_restart() with app_restart() Sukadev Bhattiprolu
2010-04-01 1:57 ` [PATCH 6/6][v3][lxc] Hook up lxc_checkpoint() with app_checkpoint() Sukadev Bhattiprolu
2010-04-01 13:24 ` [PATCH 0/6][v3][lxc] Link LXC with USERCR Cedric Le Goater
[not found] ` <4BB49E8D.1010205-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2010-04-01 16:37 ` Sukadev Bhattiprolu
[not found] ` <20100401163735.GA23231-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-01 23:36 ` Oren Laadan [this message]
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=4BB52E00.9010805@cs.columbia.edu \
--to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
--cc=clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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